Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!asp
From: asp@uunet.UU.NET (Andrew Partan)
Newsgroups: comp.protocols.tcp-ip.domains
Subject: Re: DNS glue records and BIND 4.8
Summary: unnecessary glue records cause problems
Message-ID: <106322@uunet.UU.NET>
Date: 25 Sep 90 22:15:39 GMT
References: <1918@ccadfa.adfa.oz.au> <1990Sep25.140536.16449@mp.cs.niu.edu>
Organization: UUNET Communications Services, Falls Church, VA
Lines: 18

In article <1990Sep25.140536.16449@mp.cs.niu.edu>, rickert@mp.cs.niu.edu (Neil Rickert) writes:
>  It is better to not have a glue record unless absolutely necessary, for
> otherwise this is another record which must be kept up to date, yet for
> which you are technically not responsible.

We are currently having a problem caused (I think) by someone with a
glue records for uunet.uu.net with the wrong address.  The only address
that uunet.uu.net has is 192.48.96.2; however the address 137.39.1.2
keeps showing up.

We have been trying to track this down & kill it for a while now, but
can't figure out where it is coming from.

The real problem is that named accepts non-authoratative updates for
information that it is the authoratative server for (and thus the
'infection' gets spread).  Named needs to be fixed to not do this.

	--asp@uunet.uu.net (Andrew Partan)