[Bug 484736] New: Yast does not save "forwarders" parameter in DNS setup
https://bugzilla.novell.com/show_bug.cgi?id=484736 Summary: Yast does not save "forwarders" parameter in DNS setup Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: akontsevich@gmail.com QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 Yast does not save "forwarders" parameter to /etc/named.conf in "DNS Server" setup. During settings saving Yast prints error that the parameter is missed and server could not be started. Forced to add the parameter manually to the file and restart the server manually from command line. Reproducible: Always -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=484736
Aleksey Kontsevich
https://bugzilla.novell.com/show_bug.cgi?id=484736
User chrubis@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c1
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=484736
User akontsevich@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c2
--- Comment #2 from Aleksey Kontsevich
https://bugzilla.novell.com/show_bug.cgi?id=484736
Aleksey Kontsevich
https://bugzilla.novell.com/show_bug.cgi?id=484736
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=484736
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c3
Lukas Ocilka
https://bugzilla.novell.com/show_bug.cgi?id=484736
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c4
Lukas Ocilka
https://bugzilla.novell.com/show_bug.cgi?id=484736
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c5
Marius Tomaschewski
Marius, duplicate?
When, then of bug 480334, but I don't think so. The named.conf does not include the forwarders file by default, this bug report requests to do it. And it depends on what the user exactly configured. This bug is for 11.1, this means also it is not a duplicate of the /sbin/modify_resolvconf bug: - Fixes for /etc/named.d/forwarders.conf updates in case that the file does not exists or it does not already contain a 'forwarders {};' block (bnc#134692). Regardless of bug 480334: When yast2 adds an 'include "/etc/named.d/forwarders.conf";' statement to the /etc/named.conf, it has to write a forwarders.conf (just touch it or with static forwarders, when the user requested this). It should write it _regardless_ of the NETCONFIG_DNS_FORWARDER="bind" setting (and MODIFY_NAMED_CONF_DYNAMICALLY on <= 11.0). A rcnamed restart will fail, when a file is missed. In case of netconfig _and_ when NETCONFIG_DNS_FORWARDER="bind" is alredy set, yast2 can call "netconfig update" to generate a forwarders.conf, but better is to touch the included file. Aleksey, can you describe more exactly what you've configured and what happened? Note also, that there are updates (submitted but not released yet) for sysconfig on the way - test RPMs are at: http://download.opensuse.org/repositories/home://mtomaschewski://11.1/openSU... But in case of 11.1 there is nothing related to this problem in sysconfig. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=484736
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c6
--- Comment #6 from Marius Tomaschewski
Regardless of bug 480334: When yast2 adds an 'include "/etc/named.d/forwarders.conf";' statement to the /etc/named.conf, it has to write a forwarders.conf (just touch it or with static forwarders, when the user requested this). It should write it _regardless_ of the NETCONFIG_DNS_FORWARDER="bind" setting (and MODIFY_NAMED_CONF_DYNAMICALLY on <= 11.0).
Ahm... wrong or at least not exactly. - When NETCONFIG_DNS_FORWARDER == "bind", write user's static forwarders to the NETCONFIG_DNS_STATIC_SERVERS variable, reset the forwarders.conf "cp /dev/null forwarders.conf" when the variable changed and call netconfig update to update it. (netconfig will not update it when the file contains some data, e.g. manually defined forwarders). - When NETCONFIG_DNS_FORWARDER != "bind", write users static forwarders to the forwarders.conf. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=484736
User akontsevich@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c7
Aleksey Kontsevich
Aleksey, can you describe more exactly what you've configured and what happened?
Forced to remove yast2-trans-ru for that. ;) Ok. Yast2 Control Center -> Net Services -> DNS Server -> Basic Options -> Option: Value: forward -> first -> pressed "Add" Forwarders -> {<3 DNS servers IPs listed>} -> pressed "Add" Note. Also that functionality duplicates Forwarders menu as I see. Then pressed "Ok" or Start-Up -> "Save settings and reload DNS server now". Got message: Error: Reloading name server BIND /etc/named.conf:72 no matching 'forwarders' statement. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=484736
User akontsevich@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c8
--- Comment #8 from Aleksey Kontsevich
https://bugzilla.novell.com/show_bug.cgi?id=484736
User akontsevich@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c9
--- Comment #9 from Aleksey Kontsevich
https://bugzilla.novell.com/show_bug.cgi?id=484736
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c10
--- Comment #10 from Lukas Ocilka
https://bugzilla.novell.com/show_bug.cgi?id=484736
User akontsevich@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c11
--- Comment #11 from Aleksey Kontsevich
https://bugzilla.novell.com/show_bug.cgi?id=484736
User akontsevich@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c12
--- Comment #12 from Aleksey Kontsevich
https://bugzilla.novell.com/show_bug.cgi?id=484736
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c13
Lukas Ocilka
https://bugzilla.novell.com/show_bug.cgi?id=484736
Lukas Ocilka
https://bugzilla.novell.com/show_bug.cgi?id=484736
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c14
--- Comment #14 from Marius Tomaschewski
I was able to reproduce this issue by adding --- cut --- forward first; --- cut ---
The "forward first;" (with "forwarders {};") is a default setting and can be omitted (at least on sles10). The opposite setting is "forward only;". See also Bv9ARM.ch06.html: "[...] This option is only meaningful if the forwarders list is not empty. A value of first, the default, causes the server to query the forwarders first — and if that doesn't answer the question, the server will then look for the answer itself. If only is specified, the server will only query the forwarders. [...]" Note, that in "forward first;" the queries are not forwarderd when the server knows the answer, e.g. because it has a locally defined zone that matches the query or the answer is already in the cache.
on the similar place in /etc/named.conf as Aleksey has it. I had a working forwarders setup with all the files generated...
Included forwarders just don't work in this case. Uwe, Marius, what can I do to make it work?
I don't know why I can't download the attached named.conf (comment #12), but a configuration like this should work fine: /etc/named.conf: [...] options { [...] #forward first; include "/etc/named.d/forwarders.conf"; [...] /etc/named.d/forwarders.conf: forwarders { 192.168.1.254; }; -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=484736
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c15
--- Comment #15 from Lukas Ocilka
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.
https://bugzilla.novell.com/show_bug.cgi?id=484736
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c18
--- Comment #18 from Lukas Ocilka
https://bugzilla.novell.com/show_bug.cgi?id=484736
Lukas Ocilka
https://bugzilla.novell.com/show_bug.cgi?id=484736
User akontsevich@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c19
--- Comment #19 from Aleksey Kontsevich
https://bugzilla.novell.com/show_bug.cgi?id=484736
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c20
--- Comment #20 from Marius Tomaschewski
Another bug found here: when trying to save HTTP Server settings (Apache configuration in Yast) it shows the same error as in Comment #9 - https://bugzilla.novell.com/attachment.cgi?id=279469. Why these settings are connected, or it is a serious complex bug in Yast?
I guess, the http server module makes use of the same service-restart function that shows similar looking error message or perhaps it restarts the nameserver service for some reason and runs into the same problem as here. Please open a new bug (you can use "Clone This Bug"). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=484736
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c21
--- Comment #21 from Lukas Ocilka
https://bugzilla.novell.com/show_bug.cgi?id=484736
User akontsevich@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c22
--- Comment #22 from Aleksey Kontsevich
HTTP Server is affected by the same error because it actually uses DNS Server for storing and changing DNS Records.
Then need to fix only in one place. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=484736
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c23
Lukas Ocilka
https://bugzilla.novell.com/show_bug.cgi?id=484736
Lukas Ocilka
https://bugzilla.novell.com/show_bug.cgi?id=484736
User swamp@suse.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c25
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=484736
Dirk Mueller
https://bugzilla.novell.com/show_bug.cgi?id=484736
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c27
Lukas Ocilka
https://bugzilla.novell.com/show_bug.cgi?id=484736
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c40
Lukas Ocilka
https://bugzilla.novell.com/show_bug.cgi?id=484736
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=484736#c41
Lukas Ocilka
participants (1)
-
bugzilla_noreply@novell.com