Bug 567341

Summary: no name resolution with browser when named is running
Product: [openSUSE] openSUSE 11.2 Reporter: Stefan Peter <stefan>
Component: YaST2Assignee: Marius Tomaschewski <mt>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: r.ems, thomas.aho, ug
Version: Final   
Target Milestone: ---   
Hardware: 64bit   
OS: openSUSE 11.2   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Stefan Peter 2009-12-26 20:55:23 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.6) Gecko/20091201 SUSE/3.5.6-1.1.1 Firefox/3.5.6

I use OpenSuse 11.2 with all patches installed which are available on 16.12.2009.
I do not get proper name resolution when I configure the network with Yast, using a static IP (192.168.0.10) AND bind (forwarder provider's DNS, plus internal zone). Name resolution on the command line is working fine: Nslookup delivers correct results for internal as well as external names. However, the browser (firefox or konqueror) does not resolve any address.

Reproducible: Always

Steps to Reproduce:
1. set up network using Yast: traditional mode, static IP address (e.g. 192.168.0.10/24), gateway 192.168.0.1 / eth0
2. use Yast DNS to configure bind, enter external forwarder (provider's DNS), define internal zone (e.g. with A record "test" 192.168.0.20)
3. open required firewall ports; keep default settings where not specified otherwise
Actual Results:  
name resolution of external AND internal addresses with nslookup works fine:
nslookup test -> 192.168.0.20
nslookup www.xyz.com -> correct IP
however, can not access www.xyz com with any browser;

The way back is not straight forward either:
- shut down named using Yast-DNS;
- enter provider's DNS in network configuration in Yast: browser still does not work;
- delete entire network configuration, reenter the identical settings incl. provider's DNS, just do not start the DNS server any more: name resolution of external addresses is fine, also with the browser; no resolution of internal addresses of course because named not running

Expected Results:  
name resolution of internal and external addresses should work with browser when network is configured with static IP address plus bind

the IDENTICAL configuration with OpenSuse 11.1 works fine
Comment 1 Stefan Peter 2009-12-26 20:59:50 UTC 
sorry I mean all patches installed available on 26.12.2009 (today)
Comment 2 Uwe Gansert 2010-01-04 12:34:52 UTC 
I think that's a netconfig problem.

yast2-network and yast2-dns both use the variable NETCONFIG_DNS_STATIC_SERVERS in /etc/sysconfig/network/config
yast2-network writes the nameservers to query into it (those should end in the resolv.conf)
yast2-dns the forwarders (those should end in the "forwarders {....}" directive in the bind config).

I'm not sure which of those two is right or if that even is a bug in netconfig, because after switching between those modules while testing, I got a resolv.conf with no "nameserver" entry anymore at all. Just a "search" entry but the NETCONFIG_DNS_STATIC_SERVERS variable was still configured.

An empty resolv.conf has worked on 11.1 so that's maybe the reason why nobody noticed the bug then. On 11.2 the fallback in the glibc for an empty resolv.conf is no longer "nameserver 127.0.0.1" like on 11.2 and that might trigger the bug.

Stefan, you might want to check your /etc/resolv.conf file. Is there an entry "nameserver 127.0.0.1" in it?

Marius, I assign this to you because the empty resolv.conf looks like a netconfig bug to me.
There might be a bug in yast2-network or yast2-dns too because I have doubts both have to use NETCONFIG_DNS_STATIC_SERVERS
Comment 3 Uwe Gansert 2010-01-07 08:46:51 UTC 
*** Bug 567877 has been marked as a duplicate of this bug. ***
Comment 5 Marius Tomaschewski 2010-01-13 12:42:09 UTC 
(In reply to comment #2)
> Marius, I assign this to you because the empty resolv.conf looks like a
> netconfig bug to me.

No, netconfig makes use of a glibc feature to ask a local running nameserver
then, see also https://bugzilla.novell.com/show_bug.cgi?id=558333#c7.

Using the _working_ glibc feature is better than explicit 127.0.0.1 and/or
::1, because the timeouts are shorter and there is no problem with ipv4
only and ipv6 only systems.

> There might be a bug in yast2-network or yast2-dns too because I have doubts
> both have to use NETCONFIG_DNS_STATIC_SERVERS

The intention of NETCONFIG_DNS_FORWARDER=bind mode is to allow update/extend
the forwarders.conf with dynamically provided settings (dhcp, ppp, ...).

Handled in https://bugzilla.novell.com/show_bug.cgi?id=561168

*** This bug has been marked as a duplicate of bug 473308 ***