On 04/12/11 10:50, walter.jontofs...@t-systems.com wrote: > you could use ipv6calc (ftp://ftp.bieringer.de/pub/linux/ipv6/ipv6calc) to > calculate the reverse strings.
Yes. Or do it 'the BIND way': dig -x 2001:7b8:c05::80:1 | grep ip6.arpa | tail -1 | awk '{print $1}' -- Marco > Im Auftrag von Michel de Nostredame >> Gesendet: Montag, 11. April 2011 20:44 >> An: bind-users >> Betreff: ipv6 PTR in zone file >> >> Hi BIND Users, >> >> I am not sure if my post here is proper or not. If not please >> kindly guide me to a correct list. >> >> I have lot of "static" IPv6 address needs to add into DNS PTR record. >> Most of them are server IP addresses and addresses on router >> interfaces. >> Compose proper PTR records, without human errors, is highly >> difficult (compares to IPv4 PTR records), as we encode some >> customer information into the address. >> >> I tried to look into bit-string and soon realized it is >> already removed from recent BIND versions. Then tried to >> search "$REVERSE" and "$INVERSE" on Google but got no much >> luck; seems not much development / discussion recently. >> >> For example, today we probably do PTR list this, >> >> $ORIGIN 0.0.0.0.0.0.d.4.1.a.1.0.1.0.0.2.ip6.arpa. >> 1.0.1.a.0.0.0.5.6.0.c.1.0.0.5.6 PTR >> xe-3-0-3-101.ar.par1.fr.netname.net. >> >> >> What I am think about is if there is any potential possibility >> to compose IPv6 PTR records in ZONE files in a little easier method? >> something like >> >> $ORIGIN $REVERSE(2001:01a1:4d00:0000).ip6.arpa. >> $REVERSE(6500:1c06:5000:a101) PTR >> xe-3-0-3-101.ar.par1.fr.netname.net. _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users