SixXS::Sunset 2017-06-06

Slow resolving of reverse addresses with traceroute6
[nl] Shadow Hawkins on Thursday, 08 September 2005 09:03:39
When testing traceroute6 on various Fedora Core systems I noted it takes quite a while for each step to be resolved. tcpdump seems to suffer form a similar delay in getting the right name for a given IPv6 address. I notice in a packet dump (tcpdump -n ....) that the request from my client to my bind 9 server takes the form of x[2001...... (or something along those lines) and not the normal 1.1.0.0.0.... notation I would expect. Should bind translate these requests or does one need to setup other zones to handle these requests?
Slow resolving of reverse addresses with traceroute6
[ch] Jeroen Massar SixXS Staff on Thursday, 08 September 2005 10:19:49
Upgrade your resolver libraries. IPv6 Reverse DNS should always be in the form of: c.7.c.7.0.2.e.f.f.f.c.d.0.1.2.0.1.0.0.0.1.0.0.0.8.3.8.0.1.0.0.2.ip6.arpa Nothing else. No ip6.int and no other weird things.
Slow resolving of reverse addresses with traceroute6
[nl] Shadow Hawkins on Thursday, 08 September 2005 14:49:45
Check. For the record: Fedora Core 1 does not do thing right. Fedora Core 3 does thing the right way.
Slow resolving of reverse addresses with traceroute6
[nl] Shadow Hawkins on Thursday, 08 September 2005 22:46:55
Upgrading requires a bit more planning. As I am a bit carefull when it comes to replacing glibc on a system. So if anyone knows of a workaround to translate this with bind or something I would appreciate a hint. Other then that I just see whenever I have enough time to bite the bullet and rebuild the systems with Fedora Core 4.
Slow resolving of reverse addresses with traceroute6
[nl] Shadow Hawkins on Friday, 16 September 2005 08:35:44
Could you point to any documentation? I have gone over most IPv6 RFC's I think but have not seen anything mentioned yet. Perhaps I just missed it and in that case I could do with a pointer. I noticed it is defined in RFC 2874 section 2.2.1 and never reversed in RFC 3152 but have not seen anything to suggest \[x..... notation is invalid.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker