Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!munnari.oz.au!news
From: news@cs.mu.oz.au (news)
Newsgroups: comp.protocols.tcp-ip.domains
Subject: Re: Embryonic connection to Nigeria??
Message-ID: <5809@munnari.oz.au>
Date: 18 Oct 90 18:21:31 GMT
Organization: Comp Sci, Melbourne Uni, Australia
Lines: 34

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.

kre