[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#731457: marked as done (libc: resolver doesn't fall back to secondary dns-server or retry, when first is ipv6 and unreachable)

Your message dated Tue, 17 Jun 2014 19:55:36 +0200
with message-id <20140617175536.GA5258@volta.rr44.fr>
and subject line Bug#731457: libc: resolver doesn't fall back to secondary dns-server or retry, when first is ipv6 and unreachable
has caused the Debian Bug report #731457,
regarding libc: resolver doesn't fall back to secondary dns-server or retry, when first is ipv6 and unreachable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
731457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731457
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc
Version: glibc
Severity: normal
Tags: ipv6

If the first entry in /etc/resolv.conf is an ipv6 address, and the second is 
an ipv4 address, then, if the ipv6 lookup fails, then  no fallback takes place 
to the secondary (or tertiary) servers.

Furthermore, if a 'search' list is specified, and an ipv6 address is 
present in the list, then no retries take place on any server.

For example, given the following in /etc/resolv.conf:

    nameserver 0100::1
    nameserver 4.4.4.4

"getent ahosts www.google.com" returns no entries. tcpdump shows that the 
secondary server is never polled, although the primary is polled twice.


Given the following in /etc/resolv.conf:

    search zzz.com
    nameserver 0100::1
    nameserver 4.4.4.4

tcpdump shows the first server being queried for www.google.com, and 
then for www.google.com.zzz.com. The secondary server is never queried 
at all (as above), and the primary is only queried once for each hostname.





-- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
Version: 2.19-2

On Thu, Dec 05, 2013 at 03:47:50PM +0000, Richard van der Hoff wrote:
> Package: libc
> Version: glibc
> Severity: normal
> Tags: ipv6
> 
> If the first entry in /etc/resolv.conf is an ipv6 address, and the second is 
> an ipv4 address, then, if the ipv6 lookup fails, then  no fallback takes place 
> to the secondary (or tertiary) servers.
> 
> Furthermore, if a 'search' list is specified, and an ipv6 address is 
> present in the list, then no retries take place on any server.
> 
> For example, given the following in /etc/resolv.conf:
> 
>     nameserver 0100::1
>     nameserver 4.4.4.4
> 
> "getent ahosts www.google.com" returns no entries. tcpdump shows that the 
> secondary server is never polled, although the primary is polled twice.
> 
> 
> Given the following in /etc/resolv.conf:
> 
>     search zzz.com
>     nameserver 0100::1
>     nameserver 4.4.4.4
> 
> tcpdump shows the first server being queried for www.google.com, and 
> then for www.google.com.zzz.com. The secondary server is never queried 
> at all (as above), and the primary is only queried once for each hostname.
> 

This bug has been fixed in version 2.19-2. Closing the bug accordingly.

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---
Reply to: