Check out the tools at DNSstuff.com. They have a first-class DNS analyzer that is cheap to free, and will tell you exactly what is broken, and what is NOT broken.
There site has been invaluable to me in not only basic troubleshooting of DNS, but the fine tuning of my DNS servers.
Everything from are the TLD nameservers working right, to is my mailserver responding in the correct RFC manner.
http://member.dnsstuff.com/amember/go.php?r=132325&i=l0
Clicking the above this is an affiliate link that gives me an absolutely tiny atta boy if you like this tool. If that bugs you, go direct to: www.dnsstuff.com
The initial diagnosis is that the SOA record for your domain is still pointing to the dns1.icann.org nameserver. This means one of two things: either the changing of the DNS record with the ISP did not go correctly, or enough time hasn’t passed to update the glue .com servers.
When your DNS domain is hosted by servers that have names in that domain (DNS1.example.com, when the domain you want to host is example.com), the register has to register nameserver records in it’s own glue database that permanently respond with the ip for DNS1.example.com. This is because the way DNS works, when a dns client looks up dns1.example.com to find the www.example.com record, it obviously has to find out the dns1.example.com address from somewhere besides your nameserver (see the circular loop here.) That’s where the registrar’s nameserver records come into play. By that I mean that you specifically tell your registrar to create a special server record (a - host record) that they host on the registration servers that says dns1.example.com is ip 192.0.0.2. Then everybody else uses that ip address to actually lookup every other bit of information about the zone that matters.
This is not a problem when your domain is hosted on somebody else’s nameservers, because they have already done this. If you host other domains on your servers besides example.com, you will NOT need to redo this process, since the dns1.example.com name servers will be able to be resolved to get the information for your www.otherexample.com domain.
Lots of stuff here, but I hope that it helps!
Post edited by: WillSargent, at: 2008/02/27 07:23<br><br>Post edited by: WillSargent, at: 2008/02/27 07:25