OK, ,I'm just starting to re-familiarize myself with WHM. I've been working with Plesk for the last few months.
I went into WHM and created a new account. When completed, the resulting information showed an IP of 66.250.86.33 and nameserver ns5.prioritycolocation.com. Isn't it supposed to show my private nameservers and their corresponding IPs?
nameservers for new accounts
Moderator: Admins
Hmm. After setting up an account, I can see in the DNS section of WHM that my nameservers have been in fact assigned to the new account. It still confuses me as to why the prioritycolocation nameserver is listed in the Results info, but at least the setup is working properly.
Here's another question. My nameserver IP is 66.250.86.216. But when I try to login to FTP up to the server, when I use that IP address as my host address, it doesn't allow me access. However, when I use 66.250.86.33, it lets me in. Isn't it supposed to work with my nameserver's IP address?
One more point. After uploading site to the server, I point my browser to http://66.250.86.216/~username/ and I can see the site. It also works with http://66.250.86.33/~username/ . Which one should I be giving to new customers to use?
Vito
Here's another question. My nameserver IP is 66.250.86.216. But when I try to login to FTP up to the server, when I use that IP address as my host address, it doesn't allow me access. However, when I use 66.250.86.33, it lets me in. Isn't it supposed to work with my nameserver's IP address?
One more point. After uploading site to the server, I point my browser to http://66.250.86.216/~username/ and I can see the site. It also works with http://66.250.86.33/~username/ . Which one should I be giving to new customers to use?
Vito
-
porcupine
- Site Admin
- Posts: 703
- Joined: Wed Jun 12, 2002 5:57 pm
- Location: Toronto, Ontario
- Contact:
This is just a little inconsistency that we've noticed in CPanel/WHM ever since we've started using it (the nameservers issue), nothing to be concerned by, just something that happens it seems.
Previous versions of WHM used to give a reseller their own ip and use that ip for all name based hosting that the reseller setup, but apparently does not do that anymore. We've put inquiries into this feature perk in the past, but have not gotten any response, i'm unaware of why this was done.
Name based accounts will be setup on the main server ip (.33), IP based accounts will show directly on the ip (no ~/username required). If you check your domain (try to ping it, it'll resolve it to the ip) you should get the ip and be able to use that directly.
Previous versions of WHM used to give a reseller their own ip and use that ip for all name based hosting that the reseller setup, but apparently does not do that anymore. We've put inquiries into this feature perk in the past, but have not gotten any response, i'm unaware of why this was done.
Name based accounts will be setup on the main server ip (.33), IP based accounts will show directly on the ip (no ~/username required). If you check your domain (try to ping it, it'll resolve it to the ip) you should get the ip and be able to use that directly.
Hi Myles:
I appreciate your reply, but I'm still a little fuzzy on it.
1. When I set up an account in WHT, I should not mess with the DNS settings, right?
2. Should I be giving the .33 IP address to my customers for access (ftp, mail, etc) ?
3. Is the only time I should be giving my nameserver IPs is when the customer needs them to initially make DNS changes with their registrar? (Normally all that is needed is the nameserver name, but a few registrars require an IP address as well)
Thanks for your help.
Vito
I appreciate your reply, but I'm still a little fuzzy on it.
1. When I set up an account in WHT, I should not mess with the DNS settings, right?
2. Should I be giving the .33 IP address to my customers for access (ftp, mail, etc) ?
3. Is the only time I should be giving my nameserver IPs is when the customer needs them to initially make DNS changes with their registrar? (Normally all that is needed is the nameserver name, but a few registrars require an IP address as well)
Thanks for your help.
Vito
-
porcupine
- Site Admin
- Posts: 703
- Joined: Wed Jun 12, 2002 5:57 pm
- Location: Toronto, Ontario
- Contact:
Thats correct vito,
1. when you create the account, just let cpanel/whm do its stuff, it'll get it done
2. your customers should be using mail.theirdomain.com and ftp.theirdomain.com as cpanel will automatically create that for them.
3. You can give away your nameserver ip addresses whenever necessary, they are not hard to find, and are not any form of secret/information that should not be openly distributed, no harm can be reasonably done by letting people know whta your nameserver ip's are.
1. when you create the account, just let cpanel/whm do its stuff, it'll get it done
2. your customers should be using mail.theirdomain.com and ftp.theirdomain.com as cpanel will automatically create that for them.
3. You can give away your nameserver ip addresses whenever necessary, they are not hard to find, and are not any form of secret/information that should not be openly distributed, no harm can be reasonably done by letting people know whta your nameserver ip's are.