We developed a web/mysql-based front-end that our noc uses for all DNS ops, so the NOC never touches zone files directly. So it was easy to just add a feature that provides additional syntax for ipv6 PTRs...
So for example in zone 0.0.0.0.d.c.b.a.8.B.D.0.1.0.0.2.ip6.arpa we can enter 0000:0000:0000:0003 PTR foo.com. and it will reverse the nibbles/remove the ":"s and put in the "."s and get generated into a zone file as needed: 3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.d.c.b.a.8.B.D.0.1.0.0.2.ip6.arpa PTR foo.com. (of course you can enter x.x.x.x... syntax too) Having a front-end also lets you do all sorts of other sanity-checking with instant feedback to avoid choking up BIND, depending on the skill level of your target "DNS admin". -Will On Fri, Oct 29, 2010 at 06:06:32PM -0700, Jeroen van Aart wrote: > Date: Fri, 29 Oct 2010 18:06:32 -0700 > From: Jeroen van Aart <jer...@mompl.net> > To: NANOG list <nanog@nanog.org> > 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
