Bug ID 1074268
Summary bind configuration inconsistencies ...
Classification openSUSE
Product openSUSE Distribution
Version Leap 42.3
Hardware Other
OS openSUSE Factory
Status NEW
Severity Normal
Priority P5 - None
Component Network
Assignee bnc-team-screening@forge.provo.novell.com
Reporter dieter.jurzitza@t-online.de
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

In current Leap 42.3 and in factory the following unexpected configuration
settings can be found:

/etc/init.d/named creates an empty file /etc/named.d/forwarders.conf on any
start/restart of named.service

/etc/netconfig.d/dns-bind is set up to configure /etc/named.d/forwarders.conf
under certain preconditions

however, in contrast to i.e. Leap 42.1 the file /etc/named.conf does not refer
to /etc/named.d/forwarders.conf any more. The configuration of the forwarders
is intended to happe in named.conf directly.

So, either the creation of the forwarders.conf - files happens but is not
wanted or the removal of the 
input /etc/named.d/forwarders.conf
line from named.conf is erratic and unintended. However it is - this ought to
be corrected because this is meaningless.
Thanks and regards


Dieter Jurzitza


You are receiving this mail because: