news@cs.mu.oz.au (news) (10/19/90)
From info-nets@think.com:
From: kre@cs.mu.oz.au (Robert Elz)
Path: cs.mu.oz.au!kre
Date: Thu, 18 Oct 90 12:52 CDT (UTC -05:00)
From: paul@kuhub.cc.ukans.edu
Message-ID: <19FF7E479BFF0077AC@kuhub.cc.ukans.edu>
I'm seeking to move discussion to info-nets@think.com (or
infonets@bitnic.bitnet) to discuss something unusual that I've found...
I'm not sure info-nets is the right list, namedroppers probably is
Non-authoritative answer:
ng nameserver = TELECOM
ng nameserver = NEXTSVR
ng nameserver = MTECV1
Authoritative answers can be found from:
TELECOM inet address = 132.254.1.11
NEXTSVR inet address = 132.254.1.6
MTECV1 inet address = 131.178.1.1
I've had exactly the same response from a query of "ZA" (South Africa).
Something is clearly wrong with at least one of the root nameservers
(not all of them return this trash). I'd guess that there is a very
bogus nameserver somewhere supplying bad data that's being picked up
one, or more, of the root servers.
Maybe someone decided it would be useful to add all of the ISO3166
country codes, or something...
Its definitely worth tracking down and fixing.
krelars@spectrum.CMC.COM (Lars Poulsen) (10/23/90)
In article <5809@munnari.oz.au> news@cs.mu.oz.au (news) writes: >From info-nets@think.com: >From: kre@cs.mu.oz.au (Robert Elz) >Path: cs.mu.oz.au!kre > Non-authoritative answer: > ng nameserver = TELECOM > ng nameserver = NEXTSVR > ng nameserver = MTECV1 > Authoritative answers can be found from: > TELECOM inet address = 132.254.1.11 > NEXTSVR inet address = 132.254.1.6 > MTECV1 inet address = 131.178.1.1 > >I've had exactly the same response from a query of "ZA" (South Africa). >Something is clearly wrong with at least one of the root nameservers >(not all of them return this trash). I'd guess that there is a very >bogus nameserver somewhere supplying bad data that's being picked up >one, or more, of the root servers. Following the reverse query path for 131.178.1.1 seems to point to a horrible mess at UTEXAS.EDU. I wonder how long this junk will float around even after it's been fixed. -- / Lars Poulsen, SMTS Software Engineer CMC Rockwell lars@CMC.COM