[Bug 192168] New: resolver cannot cope with link-local IPV6 addresses

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Jul 27 15:45:22 UTC 2014


            Bug ID: 192168
           Summary: resolver cannot cope with link-local IPV6 addresses
           Product: Base System
           Version: 10.0-STABLE
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: clint at clintarmstrong.net

Resolver works inconsistently with a link-local address in resolv.conf.

If using a link local address with an interface index, no queries for hosts
work. To reproduce:
1) Use a Link-Local address with interface identifier in /etc/resolv.conf, for
example:  fe80::1:1%em0

Expected Results: You should be able to resolve host names if a dns server is
listening on this address. You can confirm that this address can resolve names
using dig @fe80::1:1%em0 google.com. But using host

Actual Results: The host command times out and trying to ping hosts not in
cache fails because names cannot be resolved. You can confirm that this address
can resolve hosts by using dig @fe80::1:1%em0 google.com. However, a similar
test with the host command fails doing host google.com fe80::1:1%em0.

An attempted workaround is to use a Link-Local address using the in-kernel
syntax for identifying an interface. For example: fe80:3::1:1

This results in being able to resolve hosts with the host command. The dig
command does not work and reports a reply from an unexpected source as the
reply has a source address of fe80::1:1%em0. However, new hosts still cannot be
resolved for normal system operations like ping6. Only the host command

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-bugs mailing list