https://bugzilla.novell.com/show_bug.cgi?id=134692 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=134692#c32 --- Comment #32 from Marius Tomaschewski <mt@novell.com> 2009-02-13 09:31:31 MST --- Created an attachment (id=272729) --> (https://bugzilla.novell.com/attachment.cgi?id=272729) Proposed /sbin/modify_resolvconf fixes for forwarders.conf creation I found a little bit time to fix modify_resolvconf so far. - Check if the directory exists instead of forwarders.conf, so when there is no forwarders.conf but named is installed, it will be created. - Fixed creation of the forwarders.conf to not to expect any options block. [There is still legacy code in case the user changed NAMEDCONF back to /etc/named.conf]. - Add debug message about missed inclusion in /etc/named.conf [IMO it is not needed to flood the logs with this and yast2 adds the include statement as far as I read the comments correctly]. Too late for 10.2 but may go into 10.3 and 11.0 or sles10 sp3 updates... I'll submit test packages to build.opensuse.org at home:mtomaschewski:<version>/sysconfig soon. The comment in sysconfig, that the /etc/named.d/forwarders.conf is modified is fixed at least on >= 10.3. (In reply to comment #29) [...]

I find the following on two 10.1 machines, when I research why DNS resolution works badly:

Yes. A 'echo 'forwarders {};' > /etc/named.d/forwarders.conf" IMO fixed the problem in the past, the patch fixes it now too. Modifying of /etc/named.conf is a bad idea because of many reasons that are referenced in this bug report [one is, it may be not in options but in a zone block ;-)], but you can adjust the NAMEDCONF variable in /sbin/modify_resolvconf if you really want go back. -- 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.