We're getting responses from the root servers, the names just aren't resolving. From a windows NT machine the error is "Non- existent Domain". Ah, I just noticed something. The packet length for the DNS response is supposed to be 510 bytes but it's being truncated to 128. What the heck would cause that?? John ---- On Tue, 1 Oct 2002, John M. Brown (john@chagresventures.com) wrote:
Here is for L, F also seems to reply. Tested from 8 different places on the net. OTW Transit splay on the test was 8
different
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-SERVERS.NET. com. 2D IN NS F.GTLD-SERVERS.NET. com. 2D IN NS J.GTLD-SERVERS.NET. com. 2D IN NS K.GTLD-SERVERS.NET. com. 2D IN NS E.GTLD-SERVERS.NET. com. 2D IN NS M.GTLD-SERVERS.NET. com. 2D IN NS A.GTLD-SERVERS.NET. com. 2D IN NS G.GTLD-SERVERS.NET. com. 2D IN NS H.GTLD-SERVERS.NET. com. 2D IN NS C.GTLD-SERVERS.NET. com. 2D IN NS I.GTLD-SERVERS.NET. com. 2D IN NS B.GTLD-SERVERS.NET. com. 2D IN NS D.GTLD-SERVERS.NET.
;; ADDITIONAL SECTION: L.GTLD-SERVERS.NET. 2D IN A 192.41.162.30 F.GTLD-SERVERS.NET. 2D IN A 192.35.51.30 J.GTLD-SERVERS.NET. 2D IN A 192.48.79.30 K.GTLD-SERVERS.NET. 2D IN A 192.52.178.30 E.GTLD-SERVERS.NET. 2D IN A 192.12.94.30 M.GTLD-SERVERS.NET. 2D IN A 192.55.83.30 A.GTLD-SERVERS.NET. 2D IN A 192.5.6.30 G.GTLD-SERVERS.NET. 2D IN A 192.42.93.30 H.GTLD-SERVERS.NET. 2D IN A 192.54.112.30 C.GTLD-SERVERS.NET. 2D IN A 192.26.92.30 I.GTLD-SERVERS.NET. 2D IN A 192.43.172.30 B.GTLD-SERVERS.NET. 2D IN A 192.33.14.30 D.GTLD-SERVERS.NET. 2D IN A 192.31.80.30
;; Total query time: 89 msec ;; FROM: jedi.staff.chagres.net to SERVER: l.root- servers.net 198.32.64.12 ;; WHEN: Tue Oct 1 17:29:36 2002 ;; MSG SIZE sent: 21 rcvd: 453
% On Tue, Oct 01, 2002 at 07:08:37PM -0400, John Neiberger wrote:
We seem to be getting name resolution errors when we query
any
of the root servers, and this just started a hour or so ago.
Anyone else noticing a problem?
John
On Tue, Oct 01, 2002 at 07:46:00PM -0400, John Neiberger wrote:
We're getting responses from the root servers, the names just aren't resolving. From a windows NT machine the error is "Non- existent Domain".
You still haven't told us what you are trying to look up and what exact error you are getting. Until you do that, nobody is going to be able to provide you with any kind of real answer. --Adam -- Adam McKenna <adam@flounder.net> | GPG: 17A4 11F7 5E7E C2E7 08AA http://flounder.net/publickey.html | 38B0 05D0 8BF7 2C6D 110A
On Tue, 2002-10-01 at 17:46, John Neiberger wrote:
We're getting responses from the root servers, the names just aren't resolving. From a windows NT machine the error is "Non- existent Domain".
Ah, I just noticed something. The packet length for the DNS response is supposed to be 510 bytes but it's being truncated to 128. What the heck would cause that??
John
The maximum size of a DNS UDP update is 512 bytes, otherwise TCP will be utilized. A SERVFAIL response might very well be only 128 bytes. You might want to make sure your root hints file is correct. -dvd
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 ? John Brown Le Geek On Tue, Oct 01, 2002 at 07:46:00PM -0400, John Neiberger wrote:
We're getting responses from the root servers, the names just aren't resolving. From a windows NT machine the error is "Non- existent Domain".
Ah, I just noticed something. The packet length for the DNS response is supposed to be 510 bytes but it's being truncated to 128. What the heck would cause that??
John
---- On Tue, 1 Oct 2002, John M. Brown (john@chagresventures.com) wrote:
Here is for L, F also seems to reply. Tested from 8 different places on the net. OTW Transit splay on the test was 8
different
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-SERVERS.NET. com. 2D IN NS F.GTLD-SERVERS.NET. com. 2D IN NS J.GTLD-SERVERS.NET. com. 2D IN NS K.GTLD-SERVERS.NET. com. 2D IN NS E.GTLD-SERVERS.NET. com. 2D IN NS M.GTLD-SERVERS.NET. com. 2D IN NS A.GTLD-SERVERS.NET. com. 2D IN NS G.GTLD-SERVERS.NET. com. 2D IN NS H.GTLD-SERVERS.NET. com. 2D IN NS C.GTLD-SERVERS.NET. com. 2D IN NS I.GTLD-SERVERS.NET. com. 2D IN NS B.GTLD-SERVERS.NET. com. 2D IN NS D.GTLD-SERVERS.NET.
;; ADDITIONAL SECTION: L.GTLD-SERVERS.NET. 2D IN A 192.41.162.30 F.GTLD-SERVERS.NET. 2D IN A 192.35.51.30 J.GTLD-SERVERS.NET. 2D IN A 192.48.79.30 K.GTLD-SERVERS.NET. 2D IN A 192.52.178.30 E.GTLD-SERVERS.NET. 2D IN A 192.12.94.30 M.GTLD-SERVERS.NET. 2D IN A 192.55.83.30 A.GTLD-SERVERS.NET. 2D IN A 192.5.6.30 G.GTLD-SERVERS.NET. 2D IN A 192.42.93.30 H.GTLD-SERVERS.NET. 2D IN A 192.54.112.30 C.GTLD-SERVERS.NET. 2D IN A 192.26.92.30 I.GTLD-SERVERS.NET. 2D IN A 192.43.172.30 B.GTLD-SERVERS.NET. 2D IN A 192.33.14.30 D.GTLD-SERVERS.NET. 2D IN A 192.31.80.30
;; Total query time: 89 msec ;; FROM: jedi.staff.chagres.net to SERVER: l.root- servers.net 198.32.64.12 ;; WHEN: Tue Oct 1 17:29:36 2002 ;; MSG SIZE sent: 21 rcvd: 453
% On Tue, Oct 01, 2002 at 07:08:37PM -0400, John Neiberger wrote:
We seem to be getting name resolution errors when we query
any
of the root servers, and this just started a hour or so ago.
Anyone else noticing a problem?
John
"John M. Brown" wrote:
Root servers don't resolve names other than the TLD's.
Except when they do ;-) [rjoffe@layer9 rjoffe]$ dig @a.gtld-servers.net www.tombannenchev.com ; <<>> DiG 9.2.1 <<>> @a.gtld-servers.net www.tombannenchev.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58588 ;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;www.tombannenchev.com. IN A ;; ANSWER SECTION: www.tombannenchev.com. 172800 IN A 207.69.90.47 ;; AUTHORITY SECTION: tombannenchev.com. 172800 IN NS UDNS1.ULTRADNS.NET. tombannenchev.com. 172800 IN NS UDNS2.ULTRADNS.NET. ;; ADDITIONAL SECTION: UDNS1.ULTRADNS.NET. 172800 IN A 204.69.234.1 UDNS2.ULTRADNS.NET. 172800 IN A 204.74.101.1 ;; Query time: 91 msec ;; SERVER: 192.5.6.30#53(a.gtld-servers.net) ;; WHEN: Tue Oct 1 17:03:47 2002 ;; MSG SIZE rcvd: 139 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [rjoffe@layer9 rjoffe]$ dig @udns1.ultradns.net www.tombannenchev.com ; <<>> DiG 9.2.1 <<>> @udns1.ultradns.net www.tombannenchev.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37140 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;www.tombannenchev.com. IN A ;; ANSWER SECTION: www.tombannenchev.com. 86400 IN A 12.30.205.95 ;; AUTHORITY SECTION: tombannenchev.com. 86400 IN NS udns1.ultradns.net. tombannenchev.com. 86400 IN NS udns2.ultradns.net. ;; ADDITIONAL SECTION: udns1.ultradns.net. 86400 IN A 204.69.234.1 udns2.ultradns.net. 86400 IN A 204.74.101.1 ;; Query time: 26 msec ;; SERVER: 204.69.234.1#53(udns1.ultradns.net) ;; WHEN: Tue Oct 1 17:08:09 2002 ;; MSG SIZE rcvd: 139 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [rjoffe@layer9 rjoffe]$ nslookup www.tombannenchev.com Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing. Server: 204.74.78.121 Address: 204.74.78.121#53 Non-authoritative answer: Name: www.tombannenchev.com Address: 207.69.90.47 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- Rodney Joffe CenterGate Research Group, LLC. http://www.centergate.com "Technology so advanced, even we don't understand it!"(SM)
On Tue, 01 Oct 2002 17:11:00 PDT, Rodney Joffe <rjoffe@centergate.com> said:
[rjoffe@layer9 rjoffe]$ dig @a.gtld-servers.net www.tombannenchev.com
Well... a.gtld-servers.net isn't a root server (got bit by that myself a while ago ;) and even then...
tombannenchev.com. 172800 IN NS UDNS1.ULTRADNS.NET. tombannenchev.com. 172800 IN NS UDNS2.ULTRADNS.NET.
It doesn't resolve it, it just gives you 2 NS records..
[rjoffe@layer9 rjoffe]$ dig @udns1.ultradns.net www.tombannenchev.com
Which finally resolves it...
add www. to the zone and look for a A RR. then look up the A RR on one of ultra's servers Rodney's point is that the gTLD servers have bad glue data and its a PIA to get that data changed. Some folks also place www.example.com as a NS so that it will be glue and thus provide faster look up times for all those wonderful metric programs that say how wonderful you are. On Tue, Oct 01, 2002 at 10:41:09PM -0400, Valdis.Kletnieks@vt.edu wrote:
On Tue, 01 Oct 2002 17:11:00 PDT, Rodney Joffe <rjoffe@centergate.com> said:
[rjoffe@layer9 rjoffe]$ dig @a.gtld-servers.net www.tombannenchev.com
Well... a.gtld-servers.net isn't a root server (got bit by that myself a while ago ;) and even then...
tombannenchev.com. 172800 IN NS UDNS1.ULTRADNS.NET. tombannenchev.com. 172800 IN NS UDNS2.ULTRADNS.NET.
It doesn't resolve it, it just gives you 2 NS records..
[rjoffe@layer9 rjoffe]$ dig @udns1.ultradns.net www.tombannenchev.com
Which finally resolves it...
participants (6)
-
Adam McKenna -
David Van Duzer -
John M. Brown -
John Neiberger -
Rodney Joffe -
Valdis.Kletnieks＠vt.edu