Hi,
Call me a worry wart, thats okay.

I changed my name servers ip address's last saturday with network solutions, to the ip's assigned to it on my raq.

Still all nslookups fail to find the domains on the raq.

Meanwhile if I do a nslookup ns.iwebhost.ws rns1.earthlink.net the ns.iwebhost.ws resolves to the correct ip like the following:

Server: rns1.earthlink.net
Address: 207.217.126.81

Non-authoritative answer:
Name: ns.iwebhost.ws
Address: 216.234.186.250

Now if I do a nslookup on a domain ( nslookup kuplo.com rns1.earthlink.net) on the server it reports the following:

Server: rns1.earthlink.net
Address: 207.217.126.81

*** rns1.earthlink.net can't find kuplo.com: No response from server

So, I do a nslookup for the domain kuplo.com on the raq using the raq's dns and get this:

Server: ns.iwebhost.ws
Address: 216.234.186.250

Name: kuplo.com
Address: 216.234.186.253

Which is correct.

When I lookup kuplo.com on internic.net I get the following:


Domain Name: KUPLO.COM
Registrar: NETWORK SOLUTIONS, INC.
Whois Server: whois.networksolutions.com
Referral URL: http://www.networksolutions.com
Name Server: NS1.IWEBHOST.WS
Name Server: NS.IWEBHOST.WS
Updated Date: 28-dec-2000

So, obviously kuplo.com shows the name servers as ns1.iwebhost.ws and ns.iwebhost.ws

Now I lookup ns.iwebhost.ws on internic.net and get the following:

Server Name: NS.IWEBHOST.WS
IP Address: 216.234.186.250

Which again is correct.

So.......

How is it that my isp earthlink knows that ns.iwebhost.ws resolves to teh correct ip address, but none of the domains are resolved using earthlinks dns?

Just an explanation in laymans terms would be nice, since this really doesn't make logical sence to me at all at this point. If earthlinks dns can find my name servers, but not the domains, and yet everything points correctly, this leaves me baffled.

Shouldnt if earthlink can find my name server, and the domains are showing the correct name servers for my raq, then it should all be resolving at this point.

Help seriously appreciated.

Bb

Did you get this resolved? I have the same problem now. My NS are reconized as being nameservers and my domain whois is pointed to those nameservers. Verified this on 3 different ISP's, but none resolve the domain :(.

Yes it was finally resolved, Tera-Byte was blocking our DNS through their firewall, even though we sent in the pre requisite form stating we would keep up our own bind and dns, once they let our dns go through the firewall, everything worked again, and hey, it only took 18 days to fix!

Originally posted by brainbox
How is it that my isp earthlink knows that ns.iwebhost.ws resolves to teh correct ip address, but none of the domains are resolved using earthlinks dns?

Just an explanation in laymans terms would be nice, since this really doesn't make logical sence to me at all at this point. If earthlinks dns can find my name servers, but not the domains, and yet everything points correctly, this leaves me baffled.


If you're still interested in the answer at this point in time (after the problems was long solved :D ), it's because the gtld-servers also return the ip addresses of your nameservers as 'glue' records. Hence, as long as the gtld-servers are contactable, you can always resolve "subdomain" nameservers of a domain to their IP addresses.

Glue records are necessary because you'd otherwise have a chicken and egg situation. You know that ns.domain.com is authoritaive for domain.com, but how do you know what ns.domain.com is, without contacting the nameservers for domain.com?

Insidious loops can also take place if a domain's authoritative nameservers are named as a subdomain of some other domain, and that domain's authoritative nameservers are named as a domain of some other domain, etc until something comes full circle. Rare, but it happens.