Bug 237795

Summary:	dns reply 1.0.0.0 from router is not defaulted to proper IPv4 address
Product:	Red Hat Enterprise Linux 5	Reporter:	Shlomi Hazan <hzshlomi>
Component:	glibc	Assignee:	Jakub Jelinek <jakub>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	5.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-05-22 15:40:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Shlomi Hazan 2007-04-25 14:26:00 UTC

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.

Comment 1 Jakub Jelinek 2007-04-25 15:00:45 UTC

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.

Comment 2 Jakub Jelinek 2007-05-22 15:40:05 UTC

No response in almost a month, closing.