http://bugzilla.novell.com/show_bug.cgi?id=561168 http://bugzilla.novell.com/show_bug.cgi?id=561168#c shuang qiu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sqiu@novell.com AssignedTo|bnc-team-screening@forge.pr |pbaudis@novell.com |ovo.novell.com | -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=561168 http://bugzilla.novell.com/show_bug.cgi?id=561168#c2 flo gleixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|gleixner@bib-bvb.de | --- Comment #2 from flo gleixner 2009-12-08 12:43:03 UTC --- I want that the content of resolv.conf is controlled by yast network settings. It should not be overwritten by yast nameserver forwarders settings. Forwarders in bind may be different from resolvers set in network settings. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=561168 http://bugzilla.novell.com/show_bug.cgi?id=561168#c4 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |gleixner@bib-bvb.de --- Comment #4 from Jiri Srain 2009-12-09 08:37:21 UTC --- Could you be more specific when exactly does resolv.conf get overwritten? Which YaST module does so? -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=561168 http://bugzilla.novell.com/show_bug.cgi?id=561168#c Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsrain@novell.com |locilka@novell.com -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=561168 http://bugzilla.novell.com/show_bug.cgi?id=561168#c6 Marius Tomaschewski 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 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.

http://bugzilla.novell.com/show_bug.cgi?id=561168 http://bugzilla.novell.com/show_bug.cgi?id=561168#c8 --- Comment #8 from Marius Tomaschewski 2010-07-05 09:54:29 UTC --- See also feature request: fate#309036: Add checkbox to yast2-dns-server whether to use NETCONFIG_DNS_FORWARDER="bind" or not FYI, netconfig is not using the glibc feature by default any more, because of too many problems happened with this (glibc were broken, ...); there is a new NETCONFIG_DNS_FORWARDER_FALLBACK (=yes by default) variable on 11.3: - Added writing of name server addresses to /etc/resolv.conf in forwarder mode ("bind", "dnsmasq") as fallback for the moments, when the local forwarder process is stopped, e.g. during update (bnc#607511). Set NETCONFIG_DNS_FORWARDER_FALLBACK=no to revert. That is, netconfig now writes: /etc/resolv.conf: nameserver 127.0.0.1 # or another loopback addr when specified # in the NETCONFIG_DNS_STATIC_SERVERS var. nameserver ... # non-local nameserver fallback from static # or also dynamically provided settings # (<=policy resolved) forwarders.conf for bind or dnsmasq: nameserver ... # non-local nameserver from static or # dynamically provided settings (<=policy resolved) -- 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.