Forgive me for being a DNS clunkhead. <g> I honestly don't
know much about it, but I thought I'd post this to the list
because it did appear to be a problem with the root servers,
which would be A Bad Thing (tm).
Probable dumb question: if I do an nslookup from a desktop
directed at a root server, should the name eventually resolve?
Or, is a request to a root server from our DNS server a
different kind of request? I have a feeling it is and that I'm
barking up the wrong tree.
That might explain why an nslookup directed at someone else's
name server is working.
Still, that would lead us back to the original problem. Our
DNS server can't communicate with the root servers. Hmm..
Again, I apologize for being a total noob at this. I believe
that I'm misunderstanding the symptoms and using the wrong
tools to troubleshoot!
Thanks to all,
Root servers don't resolve names other than the TLD's.
OTW they don't have data for www.yahoo.com only for .com
which will point you towards the gTLD servers (listed below)
which will point you towards Yahoo's name servers.
What names are you trying to lookup ?
> We're getting responses from the root servers, the names
> aren't resolving. From a windows NT machine the error
> existent Domain".
> Ah, I just noticed something. The packet length for the
> response is supposed to be 510 bytes but it's being
> to 128. What the heck would cause that??
> > Here is for L, F also seems to reply. Tested from 8
> > places on the net. OTW Transit splay on the test was 8
> > providers.
> > Can you give a sample of the "errors" you are seeing?
> > Got a sample DIG line ??
> > John Brown
> > Le Geek
> > %dig @l.root-servers.net com ns
> > ; <<>> DiG 8.3 <<>> @l.root-servers.net com ns
> > ; (1 server found)
> > ;; res options: init recurs defnam dnsrch
> > ;; got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> > ;; flags: qr rd; QUERY: 1, ANSWER: 13, AUTHORITY: 0,
> ADDITIONAL: 13
> > ;; QUERY SECTION:
> > ;; com, type = NS, class = IN
> > ;; ANSWER SECTION:
> > com. 2D IN NS L.GTLD-
> > com. 2D IN NS F.GTLD-
> > com. 2D IN NS J.GTLD-
> > com. 2D IN NS K.GTLD-
> > com. 2D IN NS E.GTLD-
> > com. 2D IN NS M.GTLD-
> > com. 2D IN NS A.GTLD-
> > com. 2D IN NS G.GTLD-
> > com. 2D IN NS H.GTLD-
> > com. 2D IN NS C.GTLD-
> > com. 2D IN NS I.GTLD-
> > com. 2D IN NS B.GTLD-
> > com. 2D IN NS D.GTLD-
> > ;; ADDITIONAL SECTION:
> > L.GTLD-SERVERS.NET. 2D IN A 18.104.22.168
> > F.GTLD-SERVERS.NET. 2D IN A 22.214.171.124
> > J.GTLD-SERVERS.NET. 2D IN A 126.96.36.199
> > K.GTLD-SERVERS.NET. 2D IN A 188.8.131.52
> > E.GTLD-SERVERS.NET. 2D IN A 184.108.40.206
> > M.GTLD-SERVERS.NET. 2D IN A 220.127.116.11
> > A.GTLD-SERVERS.NET. 2D IN A 18.104.22.168
> > G.GTLD-SERVERS.NET. 2D IN A 22.214.171.124
> > H.GTLD-SERVERS.NET. 2D IN A 126.96.36.199
> > C.GTLD-SERVERS.NET. 2D IN A 188.8.131.52
> > I.GTLD-SERVERS.NET. 2D IN A 184.108.40.206
> > B.GTLD-SERVERS.NET. 2D IN A 220.127.116.11
> > D.GTLD-SERVERS.NET. 2D IN A 18.104.22.168
> > ;; Total query time: 89 msec
> > ;; FROM: jedi.staff.chagres.net to SERVER: l.root-
> servers.net 22.214.171.124
> > ;; WHEN: Tue Oct 1 17:29:36 2002
> > ;; MSG SIZE sent: 21 rcvd: 453
> > %
> > >
> > > We seem to be getting name resolution errors when we
> > > of the root servers, and this just started a hour or so