In message <AANLkTinUMZYp9qe0i5pHYZ72aL3XyCtvaqHjzHuTkpo2@mail.gmail.com>, Mich el de Nostredame writes:
On Fri, Oct 29, 2010 at 6:06 PM, Jeroen van Aart <jeroen@mompl.net> wrote:
I battled for a few hours getting IPv6 rDNS to work. The following tool proved to be quite helpful: http://www.fpsn.net/?pg=tools&tool=ipv6-inaddr Just in case anyone else would run into similar problems. It's not as straightforward as IPv4 rDNS. Greetings, Jeroen -- http://goldmark.org/jeff/stupid-disclaimers/ http://linuxmafia.com/~rick/faq/plural-of-virus.html
Forgive me if this is a stupid question.
I am curious that if BIND ever tried to make the DB file easier to operate under pure text-based environment. For example, allow something like following format inside zone file,
$ORIGIN 1.0.0.0.3.f.8.0.3.1.4.8.8.7.d.f.ip6.arpa. 48ff:fe35:d1bc PTR server.example.com.
Firstly you don't have enough bits for a IPv6 address specified and secondly how would you distingish that from wanting the following? 48ff:fe35:d1bc.1.0.0.0.3.f.8.0.3.1.4.8.8.7.d.f.ip6.arpa. PTR server.example.com. If you feel like writing a $6REVERSE directive please go ahead. We would be happy to accept such a patch. I would however make it take full IPv6 addresses and also take prefix syntax ((prefixlen % 4) == 0, as only nibble boundaries make sense) and allow $ORIGIN to be specified. e.g. $6REVERSE fd78:8413:830:1::/64 SOA .... $6REVERSE fd78:8413:830:1::/64 NS .... $6REVERSE fd78:8413:830:1::/64 NS .... $6REVERSE fd78:8413:830:1::48ff:fe35:d1bc PTR server.example.com. $6REVERSE $ORIGIN fd78:8413:830:1::/64 @ SOA ... @ NS ... @ NS ... one could make it more general and do both IPv4 and IPv6 ($REVERSE).
And when load the zone file, automatically (internally) interpret it as c.b.1.d.5.3.e.f.f.f.8.4.1.0.0.0.3.f.8.0.3.1.4.8.8.7.d.f.ip6.arpa. inside memory.
Regards, -- Michel~
-- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org