nanog mailing list archives
Re: IPv6 rDNS
From: Owen DeLong <owen () delong com>
Date: Mon, 1 Nov 2010 20:10:25 -0700
On Nov 1, 2010, at 4:40 PM, Mark Andrews wrote:
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.htmlForgive 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.
What would be the point of wanting that? It's not a legitimate ip6.arpa name. While I realize BIND will dutifully parse it in its current state and happily await a query for that particular name, it's not a legitimate ip6.arpa entry and no such query is going to arise from anything other than an error or abuse. In other words, while it is syntactically within the bounds of the RFC, it is semantically useless.
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).
I agree that a $REVERSE directive would be a better solution. (v4 and v6) Owen
Current thread:
- Re: IPv6 rDNS, (continued)
- Re: IPv6 rDNS Sven Olaf Kamphuis (Nov 02)
- Re: IPv6 rDNS David Freedman (Nov 02)
- Re: IPv6 rDNS Sven Olaf Kamphuis (Nov 02)
- Re: IPv6 rDNS Leo Bicknell (Nov 02)
- Re: IPv6 rDNS Curtis Maurand (Nov 02)
- Re: IPv6 rDNS Valdis . Kletnieks (Nov 03)
- Re: IPv6 rDNS Lamar Owen (Nov 03)
- Re: IPv6 rDNS Crist Clark (Nov 03)
- Re: IPv6 rDNS Sven Olaf Kamphuis (Nov 02)
- Re: IPv6 rDNS Mark Andrews (Nov 01)
- Re: IPv6 rDNS Owen DeLong (Nov 01)
- Re: IPv6 rDNS Mark Andrews (Nov 01)