https://bugzilla.novell.com/show_bug.cgi?id=484736
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c17
--- Comment #17 from Marius Tomaschewski
But the list of forwarders is NOT empty, there were one to three servers defined (included by netconfig), if they are not included but defined in the file directly, it starts working.
It works also with inclusion; tested. Please note also, there was a glibc bug in some update package -- see bug 473705 and 473308.
It seems the integration of netconfig is not complete.
No, it is complete, but it does not add any include statements to the named.conf, but just generates /etc/named.d/forwarders.conf file and calls a "rcnamed reload". The /etc/init.d/named script automatically copies the forwarders.conf into the chroot when it is included in the named.conf. [check this in your test setup!] When there is no 'include "/etc/named.d/forwarders.conf";' in options section of the named.conf, the file is not used. The bug 480334 requests to add the include statement by default, so the user does not need to add it manually any more. See also "man 8 netconfig": "[...] dns-bind This module writes the DNS nameservers as forwarders for the bind nameserver into the /etc/named.d/forwarders.conf file. Please verify that this file is included in the options section of /etc/named.conf, like: options { #forward first; include "/etc/named.d/forwarders.conf"; # [...] You can use the yast2 dns-server module to configure bind as forwarder. [...]" When yast2 adds the forwarders using an include statement as above, it has to create (at least an empty one) forwarders.conf or the rcnamed script will fail. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.