This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug network/22514] New: resolver don't iterate all search domains when reaching timeout


https://sourceware.org/bugzilla/show_bug.cgi?id=22514

            Bug ID: 22514
           Summary: resolver don't iterate all search domains when
                    reaching timeout
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: network
          Assignee: unassigned at sourceware dot org
          Reporter: i at f2light dot com
  Target Milestone: ---

To reproduce:

Set FULL content of /etc/resolv.conf with:
    nameserver 1.1.1.1 # server won't work
    search a b c
    options timeout:1 attempts:1 # reduce reproduce time

Then capture network traffic with 1.1.1.1:53(udp) and run `getent hosts test'.

Will get:
    Query AAAA test.a.
    Query AAAA test.
    Query A test.a
    Query A test.

But if we set nameserver to 8.8.8.8 and it responds correctly in time, will
get:
    Query AAAA test.a.
    Query AAAA test.b.
    Query AAAA test.c.
    Query AAAA test.
    Query A test.a.
    Query A test.b.
    Query A test.c.
    Query A test.

I have tested on Gentoo(=sys-libs/glibc-2.25-r9), Ubuntu(libc6-2.23-0ubuntu9),
CentOS(glibc-2.17-196.el7, glibc-2.12-1.209.el6_9.2). All of them behaves same.
So I report here.

Don't know it's intended or a bug. I prefer latter since it tries at least two
domains (not only one if found server unreachable).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]