[131671] in North American Network Operators' Group
RE: IPv6 rDNS
daemon@ATHENA.MIT.EDU (Lee Howard)
Mon Nov 1 10:51:44 2010
From: "Lee Howard" <lee@asgard.org>
To: "'Jeroen van Aart'" <jeroen@mompl.net>, "'NANOG list'" <nanog@nanog.org>
In-Reply-To: <4CCB6F98.6090103@mompl.net>
Date: Mon, 1 Nov 2010 10:51:23 -0400
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Since there's a thread here, I'll mention rDNS for residential users.
I'm not sure there's consensus about whether forward and reverse ought
to match (how strong a "should" is that?). I know you can't populate
every potential record in a reverse zone, as in IPv4. You can generate
records on the fly, or just not provide PTRs.
I've described options in draft-howard-isp-ip6rdns-04 but I'm not sure
enough people care whether it's published as an RFC. Discuss on
IETF's dnsop list.
https://www.ietf.org/mailman/listinfo/dnsop
Lee
> -----Original Message-----
> From: Jeroen van Aart [mailto:jeroen@mompl.net]
> Sent: Friday, October 29, 2010 9:07 PM
> To: NANOG list
> Subject: IPv6 rDNS
>
> 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
