From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.10) Gecko/20070409 CentOS/1.5.0.10-2.el5.centos Firefox/1.5.0.10 Description of problem: many routers spit 1.0.0.0 for any dns query. dns resolver does not fall back to use IPv4. the poor networked applications will hang (some forever). The user is effectively disconnected from the web !!!. The user solves the problem by reverting back to vista. Yes, windows does the simple fallback for him. It does not care for smart definitions. Just for applications that work. User smiling. Version-Release number of selected component (if applicable): bind-utils-9.3.3-8.el5 How reproducible: Always Steps to Reproduce: 1. try 2. to 3. surf Actual Results: you cant work with linux (out of the box). Expected Results: dns resolver should fall back to IPv4. OR an effective IPv6 system-wide disable option must be implemented. Additional info: ping does that! every single address failing on this bug is pinged correctly.
If the router spits 1.0.0.0 for any DNS query, then it obviously can't be used as a DNS server. Have never seen such a broken router, so it would be good if you could describe exactly in what situations it sends faulty replies and what exactly it sends - ideally tcpdump -s 0 -w dns.log of the packet exchange with the router when it sends broken reply.
No response in almost a month, closing.