Bug 894008
| Summary: | Impossible to reach any host on first try. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul Ecoffet <ecoffet.paul> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | dcbw, dennis, john5342 |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-02-05 14:40:49 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Paul Ecoffet
2013-01-10 14:05:22 UTC
I have been getting this for the last few days. Almost always failing the first time and more often than not passing the second time for a period of time (presumably cache time). Google Chrome and the like don't seem to have a problem (presumably because they aggressively retry). dig shows a FORMERR on the failed dns requests: [root@agpc ~]# dig 'www.bbc.co.uk' ;; Got bad packet: FORMERR 58 bytes b2 00 81 20 00 01 00 01 00 00 00 01 03 77 77 77 .............www 03 62 62 63 02 63 6f 02 75 6b 00 00 01 00 01 c0 .bbc.co.uk...... 0c 00 01 00 01 00 00 01 2c 00 04 d4 3a f6 5f 00 ........,...:._. 00 00 00 00 00 00 00 00 00 00 .......... Wireshark seems to show sane responses for both the successful and failed queries. The only common pattern i can see is that all the failed ones have the "Answer Authenticated" flag set and all the ones that succeed do not. After some more research it appears the DNS errors all come from my router (a BT HomeHub3 acting as a DNS forwarder/cache). It also appears the errors started around the same time as an automated firmware update on the router. Resolving addresses directly from any other DNS server or the router's own upstream servers works fine. Google Chrome also still works because it is using it's own DNS servers. It is however still odd that the packets appear to be valid and both Windows and Android have no problems at all with them. So two immediate questions arise. 1. Reporter, Are you using similar hardware? If not then mine is probably a separate bug. 2. Does somebody with more knowledge than me know if the packets in the attached pcap capture (first one working, second one failing) look valid? If not then i will have to have strong words with my ISP. The workaround i am using for the moment is setting outside DNS servers manually (e.g. 8.8.8.8 and 8.8.4.4) This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |