[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dhcp-users
Subject:    Re: Non-Octet Boundary Delegation (RFC 4183)
From:       Chris Buxton <chris.p.buxton () gmail ! com>
Date:       2011-09-24 0:09:45
Message-ID: 9959E2D8-00DD-4FF6-B9FD-48F1827DC075 () gmail ! com
[Download RAW message or body]


On Sep 22, 2011, at 5:55 AM, Станислав wrote:

> Peter,
> 
> 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 \
1.24.133.10.reverse.customer.lab, not 1.24.133.10.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.

Regards,
Chris Buxton
BlueCat Networks
_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


[prev in list] [next in list] [prev in thread] [next in thread]