Re: [dnsext] Short introduction to zone cuts?

In message <8D53F412-A917-4DB2-9B7F-527B8FDD6779@nominet.org.uk>, Ray Bellis wr
ites:
> 
> On 16 Mar 2012, at 23:36, Mark Andrews wrote:
> 
> > RFC 1034 say all you need to say for zone operators about NS record.
> 
> IMHO, there's more to it than that.
> 
> For example, if you have this in a parent zone:
> 
> 1.1.1.1.5.5.5.3.0.2.1.e164.arpa. IN NS ns1.example.com
> 
> and this in the child zone:
> 
> $ORIGIN 5.5.5.3.0.2.1.e164.arpa.
> @          SOA ...
> @          NS ns1.example.com
> 0.0.0.0    NAPTR ...
> 1.0.0.0    NAPTR ...
> 
> it currently works - the parent zone points to the right server, but the pa=
> rent and child disagree on where the zone cut is.
> 
> However with DNSSEC that is no longer possible.  There's nowhere to put the=
>  DS record.
> 
> For various historic reasons, the UK public ENUM tree has per-number NS rec=
> ords as shown above.  To make the parent and child consistent (without chan=
> ging the parent) the child server would need to have a separate zone file _=
> per number_.

No.  It needs the data to be available.  With traditional servers
this has required a zone file.  But even with named this could come
from a single database that defines the zones and their content using
DLZ.

dbjdns does this with a single flat file.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext