Non-Octet Boundary Delegation (RFC 4183)
chris.p.buxton at gmail.com
Sat Sep 24 00:09:45 UTC 2011
On Sep 22, 2011, at 5:55 AM, Станислав wrote:
> It's almos OK if mask is 21. but what if it's, for example 17? In that
> case I need to create 128 zones.
> I can use network masks in BIND (RFC 4183) but if I use such zone as
> 24-21.133.10.in-addr.arpa. DHCP doesn't recognize that 10.133.27.68
> belongs to this zone.
No can do. Don't use a network mask in a reverse zone name if you want the reverse zone to be updated by dhcpd.
However, if you redirect the standard reverse record names to a zone named such that the PTR record has the full chain of octets in the name, with nothing else before or between, then you can make it work.
In the standard reverse zone for 10.133.0.0/16:
$GENERATE 24-31 $ DNAME $.133.10.reverse.customer.lab.
That way, the final PTR record name for 10.133.24.1 is 220.127.116.11.reverse.customer.lab, not 18.104.22.168.in-addr.arpa. Then a reverse domain configured as reverse.customer.com (rather than the default in-addr.arpa) will allow dhcpd to update it.
More information about the dhcp-users