Complains about IPv6 entries in resolv.conf

[Jelmer Vernooij]

libadns currently complains about ipv6 nameservers in /etc/resolv.conf. It should parse those lines correctly and use those servers.

[Alexandre Dulaunoy (adulau)]

Ubuntu 7.10 is still affected by libadns unable to read a nameserver with a compressed IPv6 address.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 alpha?

[Brian J. Murrell (brian-interlinx)]

It's still reproducible in Intrepid, yes.

[rusivi2 (rusivi2-deactivatedaccount)]

Jelmer Vernooij thank you for taking the time to report this bug and helping to make Ubuntu better. The version of Ubuntu your using is in End of Life status. For more on this please see https://wiki.ubuntu.com/Releases The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

[Brian J. Murrell (brian-interlinx)]

I'm using

$ apt-cache policy wireshark
wireshark:
  Installed: 1.2.7-1
  Candidate: 1.2.7-1
  Version table:
 *** 1.2.7-1 0
        500 http://apt.interlinx.bc.ca/ubuntu/ lucid/universe Packages
        100 /var/lib/dpkg/status

here on Lucid and while it doesn't complain of IPv6 entries, it doesn't actually use them. In the View->Name Resolution menu the Resolve Names item is greyed-out, likely because wireshark couldn't find any IPv4 addresses for resolvers.

So, while you could close this bug out as no longer happening, it's likely more useful to change the Summary to "Fails to Utilize resolvers with IPv6 addresses".

[Gerald Combs (gerald.combs)]

Brian, it looks like the Lucid package uses c-ares instead of ADNS for asynchronous name resolution. IPv6 name server support was added to c-ares in version 1.7.1.

[Gerald Combs (gerald.combs)]

This affects Wireshark 2.0.x and earlier. Support for ADNS was removed from Wireshark in March 2016, prior to the 2.2.0 release: https://code.wireshark.org/review/c/14519/