<tt><font size=2><br>
> Ok, so I asked for a reverse DNS delegation of a /24. Let's
call it <br>
> "10.1.2.0/24" for the sake of discussion. I was expecting
to get the <br>
> following in their (parent) zone:<br>
> <br>
> 2.1.10.in-addr.arpa. 86400 IN NS my-master-1.example.com.<br>
> 2.1.10.in-addr.arpa. 86400 IN NS my-master-2.example.com.<br>
> <br>
> Instead, what they gave me was this:<br>
> <br>
> 0.2.1.10.in-addr.arpa. 86400 IN NS my-master-1.example.com.<br>
> 0.2.1.10.in-addr.arpa. 86400 IN NS my-master-2.example.com.<br>
></font></tt>
<br><tt><font size=2>> ...<br>
> <br>
> 255.2.1.10.in-addr.arpa. 86400 IN NS my-master-1.example.com.<br>
> 255.2.1.10.in-addr.arpa. 86400 IN NS my-master-2.example.com.<br>
> <br>
> Is that workable? It seems silly to me. Can I still just
set up a <br>
> single zone file like so?<br>
> <br>
> $TTL 86400<br>
> $ORIGIN 2.1.10.in-addr.arpa.<br>
> @ IN SOA my-master-1.example.com.
<br>
> hostmaster.example.com. ( 7 3600 600 3600000 86400 )<br>
> <br>
> @ IN NS my-master-1.example.com.<br>
> IN NS my-master-2.example.com.<br>
> <br>
> 0 IN A zero.example.com.<br>
> 1 IN A one.example.com.<br>
> 2 IN A two.example.com.<br>
> ...<br>
> etc.<br>
</font></tt>
<br><tt><font size=2>[should be "PTR", of course, not "A"]</font></tt>
<br><tt><font size=2><br>
> My gut feeling is that this isn't going to work and that they really
<br>
> need to delegate 2.1.10.in-addr.arpa directly, correct?<br>
</font></tt>
<br><tt><font size=2>It should actually work if you implemented as described
- some ENUM trees are delegated that way.</font></tt>
<br>
<br><tt><font size=2>However it'll break if you ever want to implement
DNSSEC. There is a mis-alignment between the zone cut as seen by
the parent and that seen by the child, hence there's no place to put the
DS records.</font></tt>
<br>
<br><tt><font size=2>Ray</font></tt>
<br>