This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
A problem about resolv in Glibc 2.11.3
- From: Rui Xiang <rui dot xiang at huawei dot com>
- To: <libc-help at sourceware dot org>, <libc-alpha at sourceware dot org>
- Date: Fri, 17 Apr 2015 11:02:24 +0800
- Subject: A problem about resolv in Glibc 2.11.3
- Authentication-results: sourceware.org; auth=none
Hi, list
I encountered a problem about resolv in Glibc 2.11.3.
while setting /etc/resolv.conf in system like this;
nameserver AAAA (incorrect ipv6 addr)
nameserver A (incorrect ipv4 addr)
nameserver B (correct ipv4 addr)
and using default option in our options.
I found using nslookup can't find server name for address B.
Through using starce to trace the process, I found the resolv didn't try to
connect the nameserver B, but also try to connect AAAA and A, right?
The same including:
1) 6X6
nameserver AAAA (incorrect ipv6 addr)
nameserver B (correct ipv4 addr)
nameserver AAAA (incorrect ipv6 addr)
2) 66X
nameserver AAAA (incorrect ipv6 addr)
nameserver AAAA (incorrect ipv6 addr)
nameserver B (correct ipv4 addr)
3) 46X
nameserver A (incorrect ipv4 addr)
nameserver AAAA (incorrect ipv6 addr)
nameserver B (correct ipv4 addr)
Except above four kinds of configuration, we can lookup the server name normally in other cases.
I don't know the detailed reasons. And any advice is welcome.
Thanks,
Rui