DNS for new accounts not working

[mccollin]

I had about a half dozen domains setup and running fine. I am trying to add four new domains and transfer them from another server. I setup the accounts in WHM, then went to the SB DNS Tool and configure them exactly the same as the ones that are working... same IP address. I then went to GoDaddy and updated the DNS servers to the SB DNS servers. After nearly a week, the domains still show up as non existent when you try to access them. The accounts are setup correctly, as I can access them fine using the hostname/~user . I can't figure out why they won't work... time is ticking... any ideas?

[QT]

Can you post a couple of these domain names? :)

[mccollin]

A domain that I have that is working is http://pdaphonehome.com .

A domain that I have which is not working (a new one) is http://smartphoneforums.com . Eventually, I intend to redirect the second one to the first, but for now I'm just trying to get it to get the server at all.

[charlie]

both domains seem to go to the same IP address and both websites seem to be working fine (except for some php errors on smartphoneforums.com).

remember that dns changes will take somewhere from 1 to 3 days to propogate.

[mccollin]

Apparantly support found something wrong in the DNS tool... amazing as I looked at it about 10 times... :confused:

It had been a week since the domain transfer.

[mccollin]

OK, are you saying that you can get to smartphoneforums.com, because I still can't get to it. The problem with the IP address was corrected, and ServerBeach Support said it should be good to go in an hour or less because it only needs to propogate within the ServerBeach DNS. It is redirected now to the other site, so you should see the same thing with both URLs (I acquired an existing site and merged them... thats why I'm doing this).

[charlie]

yes, i was able to get to both sites and when i pinged them, they responded with the same ip address, which means they are running on the same box.

[gsbe]

did you try to restarting the bind service?

I had a similar problem and I'm not sure what fixed it. I changed the ttl's on the domain name and restarted bind and that solved the problem. But, I don't know which actually worked, so try restarting bind first. I don't think that changing ttl's is really making any difference at all.

A simple site that will help you diagnose common DNS problems and provide a full report of your DNS info for individual domains can be found here:
http://www.DNSreport.com

Additionally, a great online toolset for DNS can be found here:
http://www.dnsstuff.com