Red Hat Bugzilla – Bug 237795
dns reply 220.127.116.11 from router is not defaulted to proper IPv4 address
Last modified: 2007-11-30 17:07:43 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:18.104.22.168) Gecko/20070409 CentOS/22.214.171.124-2.el5.centos Firefox/126.96.36.199
Description of problem:
many routers spit 188.8.131.52 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):
Steps to Reproduce:
you cant work with linux (out of the box).
dns resolver should fall back to IPv4.
an effective IPv6 system-wide disable option must be implemented.
ping does that!
every single address failing on this bug is pinged correctly.
If the router spits 184.108.40.206 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.