Created attachment 347515 [details] pcap file containing DNS lookup Description of problem: I have a friend running Fedora 11. Her home network uses a Netopia 3347-02 DSL router provided by Qwest. Its DNS server seems to behave badly with IPv6 queries, which prevents most applications from working. Her machine has no search domain specified in /etc/resolv.conf; only the single name server (192.168.0.1) is listed in that file. For some reason, glibc seems to be doing a lookup for FQDNs in the host's "domain", which I don't understand. For example, if I try to ssh to "home.dragonsdawn.net", glibc ends up doing a query for "home.dragonsdawn.net.localdomain." A pcap file showing exactly this exchange is attached. Version-Release number of selected component (if applicable): glibc-2.10.1-2.i686 How reproducible: Always. Affected applications are unable to ever successfully look up hostnames.
If you have a buggy router, try to add options single-request to /etc/resolv.conf.
That'd be fabulous, but NetworkManager would just over-write it. Two questions: Does the pcap file attached match the specific problem that "options single-request" is designed to work around? Why does glibc look up hostnames with an appended domain, even though /etc/resolv.conf doesn't specify any search domain?
(In reply to comment #2) > That'd be fabulous, but NetworkManager would just over-write it. That shouldn't happen. NM shouldn't touch the options. I'm closing the bug. Only reopen if you verified that what Jakub explained doesn't work for you.
It took me a long time to get more data after my friend dropped Fedora for Ubuntu, which doesn't demonstrate this problem. I'm not sure how to make NetworkManager not touch options. 1. edit resolv.conf with Jakub's suggestion 2. unplug ethernet cable (assuming you're using an ethernet connection) 3. check resolv.conf. It's empty (except for comments) 4. plug in ethernet 5. check resolv.conf again. No "options". That aside, this problem is not resolved using the single-request option. Please check the pcap file that I provided. It shows that an A request gets a proper response, an A4 request gets an empty response, and then an A request is made for the hostname that the application wanted + the local host's "domain" (as returned by 'hostname -d'). I don't understand why the last request is made. The appended domain is not in the search domain, and the original A request got a valid response.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug still affects Fedora 14.
A user on the fedora users list reported a similar problem. I believe that this bug manifests when the DNS server does not support recursive queries for AAAA requests. The user provided this information: --- Sending "dig -t aaaa google.com" to my local DNS server: ; <<>> DiG 9.7.2-P2-RedHat-9.7.2-2.P2.fc14 <<>> -t aaaa google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39018 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: recursion requested but not available --- That's consistent with the Netopia router's behavior. So for some reason when the DNS server indicates that recursion is not available for AAAA requests, glibc is throwing away the results that it got from the A request.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
*** Bug 746086 has been marked as a duplicate of this bug. ***
*** Bug 720877 has been marked as a duplicate of this bug. ***
*** Bug 602396 has been marked as a duplicate of this bug. ***
*** Bug 677093 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 697149 ***