http://bugzilla.novell.com/show_bug.cgi?id=561168 http://bugzilla.novell.com/show_bug.cgi?id=561168#c6 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@novell.com Component|Basesystem |YaST2 Version|Final |Factory AssignedTo|mt@novell.com |locilka@novell.com Product|openSUSE 11.2 |openSUSE 11.3 Severity|Normal |Enhancement --- Comment #6 from Marius Tomaschewski <mt@novell.com> 2009-12-16 08:38:15 UTC --- There is the NETCONFIG_DNS_FORWARDER variable that can be "resolver", "bind" or "dnsmasq". It controls where to write the NETCONFIG_DNS_STATIC_* and/or dynamic (dhcp, ppp provided) name servers. See also "man 8 netconfig". "resolver": writes search list and name server list to /etc/resolv.conf "bind" : writes search list to /etc/resolv.conf and name servers to the /etc/named.d/forwarders.conf, that is there are no name servers in /etc/resolv.conf then. Netconfig makes use of a glibc feature to contact the local nameserver automatically, that seems to be broken again, see bug 473308 and bug 558333. "dnsmasq" : analogue to bind (In reply to comment #5)
Steps to reproduce: yast2 -> Network Settings -> Tab Hostname/DNS -> Name Server 1-3: set up some name servers
The result is: These name servers are written to /etc/resolv.conf
OK.
Then call yast module "DNS Server". Accept installing bind if not yet installed. You see the name server set up before in the List of forwarders. I want to delete this, because i want have another dns server for redundancy. -> Delete forwarders. Step through the rest of the wizard and finish.
Result: resolv.conf has no nameserver entry <- This should not happen!
This is a feature of glibc, not a bug.
Back to yast2 -> Network Settings -> Tab Hostname/DNS -> Name Server 1-3: set up nameserver again (including now 127.0.0.1 as we have a new nameserver).
Result: resolv.conf has no nameserver entry <- This should not happen!
same as above.
Resolver and forwardes for dns server are not the same thing.
No, they aren't -- the recursive nameservers in resolv.conf are used by the glibc, the recursive nameservers in forwarders.conf are used by bind only. glibc makes automatically use of a local nameserver (bind here) when there are no nameservers in resolv.conf. Further, when bind is set to "forwarders first;", it is using the forwarders first and makes a fall back to full recursion using root name servers.
Usually they are set up with the same entries, but in many cases this is not useful (redundant name servers, specialized name servers, ...)
As Lukas already wrote in https://bugzilla.novell.com/show_bug.cgi?id=558333#c2 it is a feature, not a bug. Which name server settings are written to resolv/forwarders.conf, you can specify using the NETCONFIG_DNS_POLICY. When you set NETCONFIG_DNS_POLICY="STATIC" (instead of "auto"), only the name server specified in the NETCONFIG_DNS_STATIC_* variables are used. That yast2 dns-server writes the forwarders to NETCONFIG_DNS_STATIC_* and sets NETCONFIG_DNS_FORWARDER to "bind" is OK -- a feature. Well, it would be possible to add a checkbox that makes this feature optional and causes to keep the NETCONFIG_DNS_FORWARDER="resolver" and write the nameserves directly to the forwarders.conf instead. Then you can decide yourself in netconfig variables how to handle the nameservers for resolv.conf and forwarders.conf. I'm changing to enhancement for 11.3 and reassign to Lukas to review it. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.