[131699] in North American Network Operators' Group
Re: IPv6 rDNS
daemon@ATHENA.MIT.EDU (Owen DeLong)
Mon Nov 1 21:09:17 2010
From: Owen DeLong <owen@delong.com>
In-Reply-To: <AANLkTinUMZYp9qe0i5pHYZ72aL3XyCtvaqHjzHuTkpo2@mail.gmail.com>
Date: Mon, 1 Nov 2010 18:06:46 -0700
To: Michel de Nostredame <d.nostra@gmail.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Nov 1, 2010, at 11:20 AM, Michel de Nostredame wrote:
> 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.
>
> 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.
>
>
If you're going to do that, why not make it possible to declare:
$ORIGIN fd78:8413:38f:1::.ip6.arpa as well?
Owen
