On 11/09/2011 21:00, [email protected] wrote: > I also think the creation of the reverse zone ipv6 > > i dont know how to
IPv6 reverse zones work in very much the same way as IPv4 reverse zones.
So, for an address 2001:8b0:151:1:e2cb:4eff:fe26:6481 you would generate
the LHS of a PTR record like so:
1.8.4.6.6.2.e.f.f.f.e.4.b.c.2.e.1.0.0.0.1.5.1.0.0.b.8.0.1.0.0.2.ip6.arpa
Expand each colon separated field to 4 digits by inserting leading
zeros, drop the colons, reverse the order of the whole thing, add dots
between each hex digit and tack on .ip6.arpa on the end. Or use
arpaname(1) which comes with bind.
You'll need to have the reverse zone delegated to you -- usually by your
ISP and usually on the same /48 or /64 boundary used in routing. Unlike
with IPv4, each label only counts for 16 addresses which is very much
less than the total of a typical allocation, so RFC 2317 style
delegation should become extinct. Assuming you have $ORIGIN as
1.0.0.0.1.5.1.0.0.b.8.0.1.0.0.2.ip6.arpa, then a typical PTR record in
your zone file might look like:
1.8.4.6.6.2.e.f.f.f.e.4.b.c.2.e PTR ns0.infracaninophile.co.uk.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: [email protected] Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/bind-users
