reverse dns for IPV6 ranges

Jay Ford jay-ford at uiowa.edu
Mon Mar 19 22:16:04 UTC 2012


On Mon, 19 Mar 2012, hugo hugoo <hugobxl at hotmail.com> wrote:
>  Jay,
>
> - Can you give me an example of such configuration?

Sure.

Say I use a DHCP pool of </64_prefix>:a123:b456::/96 within each /64 subnet.

For example:
    subnet             DHCP pool
    _________________  ___________________________
    2001:db8:0:a::/64  2001:db8:0:a:a123:b456::/96
    2001:db8:0:b::/64  2001:db8:0:b:a123:b456::/96
    2001:db8:0:c::/64  2001:db8:0:c:a123:b456::/96

Then you put this in every /64 subnet zone:
;____________________________________________________________
*.6.5.4.b.3.2.1.a	IN	PTR	dhcpv6.whatever.edu.
;____________________________________________________________

so that PTR queries for addresses like:
    2001:db8:0:a:a123:b456::4
    2001:db8:0:b:a123:b456:1:2
    2001:db8:0:c:a123:b456:abc:def
all return "dhcpv6.whatever.edu".

To make that less tedious, I create a file called "dhcpv6.ptr.inc" like this:

;____________________________________________________________
; dhcpv6.ptr.inc
; include file defining wildcard PTR record for DHCPv6 pools
$TTL 86400
@	IN	PTR	dhcpv6.whatever.edu.
;____________________________________________________________

Each subnet zone file (e.g., zone a.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa
for subnet 2001:db8:0:a::/64) pulls in that file via:

;____________________________________________________________
$INCLUDE dhcpv6.ptr.inc *.6.5.4.b.3.2.1.a
;____________________________________________________________

That way if I want to change the name in the PTR record I edit 1 file instead
of every zone file.

________________________________________________________________________
Jay Ford, Network Engineering Group, Information Technology Services
University of Iowa, Iowa City, IA 52242
email: jay-ford at uiowa.edu, phone: 319-335-5555, fax: 319-335-2951



More information about the bind-users mailing list