Looking for DNS/Operational experience

Steve Bertrand steve at ibctech.ca
Fri May 8 07:44:11 CEST 2009

Tore Anderson wrote:
> Hello,
> * Steve Bertrand
>> - any UNIX command-line tool to convert a compressed v6 addr into a 
>> reverse DNS entry
> I've used "dig" for this.  It's not exactly what it's built for but it
> gets the job done:
> tore at envy:~$ dig -x 2a02:c0:100::2 +noall +question
> ; <<>> DiG 9.5.1-P2-RedHat-9.5.1-2.P2.fc10 <<>> -x 2a02:c0:100::2 +noall +question
> ;; global options:  printcmd
> ; IN PTR

Thanks for all the feedback thus far.

I've been weighing options in all regards (v6-wise), and I'm finding
things to be difficult.

I'm a FreeBSD person (not strictly, but inherently), and am just now in
the process of building a bunch of jails so I can give them out to

Reverse DNS for my v6 wasn't important to me, until I turned up my third
BGP feed, and realized that my traces were taking a while on a
particular hop:

pearl# traceroute6 ipv6.google.com
 2  2607:f118:1:2:211:bbff:fe58:4240  0.982 ms  0.812 ms  0.979 ms

The IP is one of my edge devices that 'pearl' is closely connected to.
My PtP connections between P and PE are /64 eui, and iBGP is across

Loopbacks are defined and documented:

2607:f118::c1 == P1
2607:f118::c2 == P2
2607:f118::e1 == PE1
2607:f118::e2 == PE2


The PtP (I don't have a distribution layer... I'm very small, and
although I'm sure of my ability to ``insert'' one, I'm still open to
advice as to why I need one) are within the x:x:1:x scope. For instance:

2607:f118:1:1 == P1 - P2
2607:f118:1:2 == P1 - PE2
2607:f118:1:3 == P1 - PE3

My scope in the grand scheme of things is very minute (/21 & /32), but I
feel quite honoured to be a part of IPv6, and I take great pride in it.

I've recently registered ipv6canada.com (which gave me glue for my
personal .ca domain), and onlyv6.com, which I'm using as literally a v6
only domain for statistics gathering thanks to FBSD & IPv6 capable
jails. Neither domain is completely standards-compliant, but they will
be within a couple of days.

Even during the writing of this long-drawn out message, I've got several
responses... thanks ;)

What I propose, and what I am going to work on, is a tool that will:

- look at the router (SNMP, RANCID gatherings, or otherwise)
- identify the interface and locale details of the router
- turn the IP 2607:f118:1:2:211:bbff:fe58:4240 into a DNS fwd & rev name
(information on proper interface naming standards for a real ISP welcome...)
- have the tool integrate with both BIND and TinyDNS

I also plan on moving forward with IPv6 no matter who says what, and I
plan on learning from every single mistake that I make, so I might be
able to provide the next person with information so they can progress
the protocol one step further than I was able to.


More information about the ipv6-ops mailing list