You can access your server through cPanel/WHM correct? So this eliminates the possibility that your own personal IP has been blocked by the server? Have you asked a friend or co-worker if they can ping the address to see if it's just your end? Was the server working before and this issue just occurred? Any more information can help with getting the best answer on this issue
█ EQHosting - Experience the Difference
█ Web Hosting - Game Servers - Ventrilo Servers - Dedicated Servers
█ 24/7 Support - Instant Setup - 99.9% Uptime Guarantee
█ EQHosting.com - Twitter
Thats correct - all you have to do is wait for the propogation to complete.
Some registrars also require you to inform them if you are using child-nameservers (as in your case), however, very few do - this is just so that they can include them in their DNS records for propagation.
Pinging the site would mean you would be pinging your primary shared (new) IP address - NOT the domain name (which will have not fully propagated). You can also check DNS propagation of your domain name by using any of the tools available online (just google "dns propagation checker")
I presume you mean your primary shared IP is down?
Have to tried rebooting your server after you completed the setup in WHM? Are you getting any "failed services" messages?
Your nameservers are coming up, but seems your IPs are not responding, which most likely means a server-side issue either with the "named" service or similar - a simple reboot might solve the problem.
Well, the DNS seems to have propagated fine - however your nameserver IPs are failing - so, definitely is an issue with the "named" service on your server.
Last edited by CreativHost; 08-18-2009 at 04:30 PM.
Well, the site would show up from the "old" server IF the dns was resolving (pointing) to it ... in your case, it is now pointing to your "new" server ...
And as you said, if the site is loading up via IP/~userID - then it's definitely your DNS on the server which is failing ... have to rebooted the server / or at least restarted Apache & named services?
Should the nameservers for sure be setup as the next 2 IPs after the main IP address? For instance main IP is xxx.51.234.156. So should the nameservers be setup under xxx.234.51.157 & xxx.234.51.158, or doesn't it matter?
Weird thing now, is when I visit just the primary shared IP address WITHOUT the IP/~userID/ it pulls up 1 of the sites I'm hosting. I thought if you typed in a primary IP without the /~userID/ nothing should show up?
Are you comfortable with SSH access on your server? Check your ns1.xxx.com.db and ns2.xxx.com.bd files to ensure the IP binding it there against the nameserver records location
Also, is your resolver.cnf setup to your DC's resolver IP?