Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!mp.cs.niu.edu!rickert
From: rickert@mp.cs.niu.edu (Neil Rickert)
Newsgroups: comp.protocols.tcp-ip.domains
Subject: Re: Is a glue record required here ?
Message-ID: <1991Apr19.174659.20441@mp.cs.niu.edu>
Date: 19 Apr 91 17:46:59 GMT
References: <1210@nikhefh.nikhef.nl>
Organization: Northern Illinois University
Lines: 29

In article <1210@nikhefh.nikhef.nl> e07@nikhefh.nikhef.nl (Eric Wassenaar) writes:
>$ORIGIN foo.bar.
>@		IN	SOA	...
>		IN	NS	host1.foo.bar.
>sub2		IN	NS	host2.foo.bar.
>sub1		IN	NS	host3.sub2.foo.bar.

>The question is here whether or not to add a glue record for
>'host3.sub2.foo.bar' on behalf of subsequent queries such as
>'host4.sub1.foo.bar'.

>Is a glue record for host3 in this case
>a. absolutely necessary
>b. redundant but a time-saving handy shortcut
>c. plainly wrong

  My vote is for (c.).  Otherwise when the data (for example the A-record)
for host3 is changed, somebody has to remember to update the glue record,
and it is too easy for that to be overlooked.

  In most practical situations the current host would probably be a
secondary nameserver for the sub2 and sub1 subdomains, in which case it
would happen to have the necessary A-record available anyway.

-- 
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
  Neil W. Rickert, Computer Science               <rickert@cs.niu.edu>
  Northern Illinois Univ.
  DeKalb, IL 60115                                   +1-815-753-6940