Non-Octet Boundary Delegation (RFC 4183)

[Simon Hobson]

Stas’ wrote:
>I've tried to use "zone 0-25.0.16.172.in-addr.arpa." for a reverse
>zone but it didn't work.

No it won't. The reverse zone config option sets 
the *base* to which dhcpd adds the reversed 
address - so in your case it would (I believe) 
try and update 
n.0.16.172.0-25.0.16.172.in-addr.arpa.

Bear in mind that the technique you quote does 
not in fact rely on any hard-codes support for it 
- it's merely a use of PTR records to add a 
second level of indirection, 
n.0.16.172.in-addr.arpa has a PTR record to 
n.0-25.0.16.172.in-addr.arpa, and ns records 
allow the client to then query another server to 
map n.0-25.0.16.172.in-addr.arpa back to a FQDN.

If you read section 6, it mentions using 
alternate domain names - in-addr.arpa is only 
really a convention to make all the reverse zones 
easily findable from the root, and since you are 
running a custom bit of reverse zone with 
pointers to it's records, you can put this 
anywhere (such as reverse.mydomain.tld - but 
obviously using real names !).

So if you run your own alternate reverse domain 
tree under reverse.yourdomain.com, then you can 
get the owner of 0.16.172.in-addr.arpa to create 
pointer records to 
0.16.172.reverse.yourdomain.com for the addresses 
you use, and let dhcpd update that zone by 
setting the reverse zone root to 
reverse.yourdomain.com.

-- 
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.