Re: [dnsext] Short introduction to zone cuts?

On 03/17/2012 06:31, Ray Bellis wrote:
> 
> 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 parent and child disagree on where the zone cut is.

I'm not sure what you mean by "works" here. If you mean that anyone
using ns1.example.com directly will see those records, then yes, it
works -- for those users. But assuming that ns1.example.com is not
included in the NS set of the parent zone, no one else will see the 2
NAPTR records you listed above. So in that sense it doesn't work ... at
least, it doesn't work the way that the administrator of ns1.example.com
wants it to.

Doug

-- 
    If you're never wrong, you're not trying hard enough
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext