|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast-DNS-Server changes NETCONFIG_DNS_FORWARDER to bind, so /etc/resolv.conf has no nameserver entries | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Joe Morris <joe_morris> |
| Component: | YaST2 | Assignee: | Marius Tomaschewski <mt> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | eddie, ihno, locilka, mc |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Joe Morris
2009-02-08 08:48:07 UTC
I just also thought of one important thing, the info in resolv.conf if running a local DNS server should have nameserver 127.0.0.1, but not the forwarders.conf. So the NETCONFIG_DNS_STATIC_SERVER variable can be either the DNS forwarders OR the nameservers for resolv.conf. In previous versions, it was possible to append the local nameserver to what was added to resolv.conf. I do not see a way to do this anymore. So if the variable NETCONFIG_DNS_FORWADER is set to bind, then nameserver 127.0.0.1 should always be appended to nameserver entries in resolv.conf in my thinking. I'm assuming this is the same as my experience. I ran some updates and found it broke in the middle of the process and couldn't find the hosts. All networking activities seem to cease except for nslookup. Eventually, I discovered that the resolv.conf was void of nameservers despite the fact that I had name servers listed in the network devices section of yast. For me this was a show-stopper, however I was able to get things going by manually editing the resolv.conf file and listing my nameservers. It looks like something in the system changed between the time of
the implementation & tests in netconfig and the 11.1 release time.
It should be not needed to set any nameserver in /etc/resolv.conf:
From man resolv.conf(5):
nameserver Name server IP address
Internet address (in dot notation) of a name server that the
resolver should query. Up to MAXNS (currently 3, see
<resolv.h>) name servers may be listed, one per keyword. If
there are multiple servers, the resolver library queries them in
the order listed. If no nameserver entries are present, the
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
default is to use the name server on the local machine. (The
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
algorithm used is to try a name server, and if the query times
out, try the next, until out of name servers, then repeat trying
all the name servers until a maximum number of retries are
made.)
In fact, not setting any, has had the advantage, that the resolver
was trying to reach the nameserver on local machine via IPv4 and
IPv6, so it was not needed to check if IPv6 is enabled or not or
limit it to use IPv4 only.
Because of this fact, we also don't set any in netconfig.
On my 11.0 and SLES-10 systems not settings any still works fine...
This is a bug in the latest glibc maintenance update for 11.1; there is another one going through the QA triage for some time now, with this fixed. SLE11 might be affected in some RC but should have this fixed right now. Resolving as duplicate. *** This bug has been marked as a duplicate of bug 473308 *** |