Re: Should a nameserver know about itself?

[Bruce Campbell <bruce.campbell@apnic.net>]

On Wed, 30 May 2001, Robert Elz wrote:

>     From:        Shane Kerr <shane@ripe.net>
> 
>   | Remember that registries are concerned with address to name mapping, and
>   | this is a name to address mapping - one that is already performed
>   | elsewhere.
> 
> This has nothing to do with anything.   Anyone delegating pieces of the
> DNS tree (whether for profit, as a public service, or just to other parts
> of their own organisation) ought to be doing it properly.   And that
> includes inserting glue records whenever they are required.

Then (taking into account the RIR's previous experience with glue records
and the resounding lack of people caring about the reverse tree etc), what
would be the 'best' way of doing this?

The RIR's current procedures for obtaining delegation information are
simply 'range, nameservers' (in one form or another).  Asking the RIRs to
supply glue with the delegation implies an extra step, with accompanying
onus, being one of:

	Nameserver IPs collected at time of request, onus on
	client/requestor to ensure that they are kept up to date.

or

	RIR automagically keeps track of IP address changes applicable to
	nameservers referenced as glue, with onus on RIR to keep this
	magic running  (assume normal DNS refresh times are involved here,
	so a change to a glue nameserver would be reflected in the RIR's 
	glue a short (Listed-DNS-refresh-time+Listed-RIR-zone-rebuild-time)
	time later ).

or

	(current) RIR does not supply glue records, relying on the
	visibility of the forward tree for delegations to work.

Choose one, you can't have all three ;)

-- 
  Bruce Campbell <bruce.campbell@apnic.net>                +61-7-3367-0490
                      Systems Administrator                          APNIC