To:
dnsop@cafax.se
From:
James Raftery <james@now.ie>
Date:
Thu, 31 May 2001 17:01:31 +0100
Content-Disposition:
inline
In-Reply-To:
<Pine.BSI.4.05L.10105311148580.26280-100000@x17.ripe.net>; from shane@ripe.net on Thu, May 31, 2001 at 12:29:09PM +0200
Mail-Followup-To:
dnsop@cafax.se
Sender:
owner-dnsop@cafax.se
User-Agent:
Mutt/1.2.5i
Subject:
Re: Should a nameserver know about itself?
On Thu, May 31, 2001 at 12:29:09PM +0200, Shane Kerr wrote: > True, they won't have to update > the information very often once correct, but every time they buy a > smaller ISP they're going to have to worry about not only integrating > the different infrastructure into their own, but also now changing a set > of records in one or more RIR databases to use their preferred name > servers. True; but it's their choice. I don't think anybody's suggesting ISPs must do it. If I choose to use such a naming scheme for my delegations then it's up to me to make sure it works. The problem now is that even though it's perfectly legal and reasonable there are RIRs that won't let me do it. > Does anyone who administers a lot of IP space have strong feelings on > this issue? Yes; if there is any RIR that can't/won't put glue A records into IN-ADDR.ARPA zones in cases where such glue should be there (thereby preventing the use of in-zone nameservers for the NS records) that constitutes a problem that needs to be fixed. Whether or not DNS administrators choose to use such a naming/delegation scheme is entirely irrelevant. Regards, james -- James Raftery (JBR54) "It's somewhere in the Red Hat district" -- A network engineer's freudian slip when talking about Amsterdam's nightlife at RIPE 38.