Yast breaks named startup

jwoodring · March 20, 2017, 10:55pm

I have a system on an isolated network which supplies local DNS to workstations via named. I have been working in SLES for years without issue. In creating a new install on Leap 42.2, I have noticed that named wasn’t restarting at boot. After looking into this, it “seems” that Yast activity (specifically accessing the “DHCP Server” function) breaks the startup config for named (DNS in Yast).

Looking at the systemctl info for named.service, I see Yast stoping named upon entry to “DHCP Server” but it never restarts when you exit “DHCP Server”. If I go back in to the DNS Server (in Yast) and reset the parameters for “Start at boot” and “Start Now” it functions and survives a reboot.

I have seen no mention of this in any forum or Internet search. Is this a known issue?

Here’s some initial system info.
Uname -a:
Linux fredc 4.4.49-16-default #1 SMP Sun Feb 19 17:40:35 UTC 2017 (70e9954) x86_64 x86_64 x86_64 GNU/Linux

Systemctl named status:
● named.service - LSB: Domain Name System (DNS) server, named
Loaded: loaded (/etc/init.d/named; bad; vendor preset: disabled)
Active: active (running) since Mon 2017-03-20 15:56:35 CDT; 8min ago
Docs: man:systemd-sysv-generator(8)
Process: 1943 ExecStart=/etc/init.d/named start (code=exited, status=0/SUCCESS)
Tasks: 35 (limit: 512)
CGroup: /system.slice/named.service
└─2309 /usr/sbin/named -t /var/lib/named -u named

Mar 20 15:56:35 fredc named[2309]: automatic empty zone: B.E.F.IP6.ARPA
Mar 20 15:56:35 fredc named[2309]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Mar 20 15:56:35 fredc named[2309]: automatic empty zone: EMPTY.AS112.ARPA
Mar 20 15:56:35 fredc named[2309]: configuring command channel from ‘/etc/rndc.key’
Mar 20 15:56:35 fredc named[2309]: command channel listening on 127.0.0.1#953
Mar 20 15:56:35 fredc named[2309]: configuring command channel from ‘/etc/rndc.key’
Mar 20 15:56:35 fredc named[2309]: couldn’t add command channel ::1#953: address not available
Mar 20 15:56:35 fredc named[1943]: Starting name server BIND …done
Mar 20 15:56:35 fredc systemd[1]: Started LSB: Domain Name System (DNS) server, named.
Mar 20 16:00:01 fredc systemd[1]: Started LSB: Domain Name System (DNS) server, named.

systemctl -u named.service:
– Logs begin at Wed 2017-03-01 11:26:51 CST, end at Mon 2017-03-20 16:11:18 CDT. –
Mar 20 15:56:33 fredc systemd[1]: Starting LSB: Domain Name System (DNS) server, named…
Mar 20 15:56:35 fredc named[2309]: starting BIND 9.9.9-P1 (Extended Support Version) <id:99ed57a> -t /var/lib/named -u named
Mar 20 15:56:35 fredc named[2309]: running on Linux x86_64 4.4.49-16-default #1 SMP Sun Feb 19 17:40:35 UTC 2017 (70e9954)
Mar 20 15:56:35 fredc named[2309]: built with ‘–prefix=/usr’ ‘–bindir=/usr/bin’ ‘–sbindir=/usr/sbin’ ‘–sysconfdir=/etc’ ‘–localstatedir=/var’ ‘–libdir=/usr/lib64’ ‘–includedir=/usr/include/bind’ ‘–mandir=/usr/share/man’ ‘–infodir=/usr/share/info’ ‘–disable-static’ ‘–with-openssl’ ‘–enable-threads’ ‘–with-libtool’ ‘–enable-runidn’ ‘–with-libxml2’ ‘–with-dlz-mysql’ ‘–with-dlz-ldap’ ‘–enable-rrl’ ‘–enable-fetchlimit’ 'CFLAGS=-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -DNO_VERSION_DATE -fno-strict-aliasing ’ ‘LDFLAGS=-L/usr/lib64’
Mar 20 15:56:35 fredc named[2309]: ----------------------------------------------------
Mar 20 15:56:35 fredc named[2309]: BIND 9 is maintained by Internet Systems Consortium,
Mar 20 15:56:35 fredc named[2309]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
Mar 20 15:56:35 fredc named[2309]: corporation. Support and training for BIND 9 are
Mar 20 15:56:35 fredc named[2309]: available at https://www.isc.org/support
Mar 20 15:56:35 fredc named[2309]: ----------------------------------------------------
Mar 20 15:56:35 fredc named[2309]: adjusted limit on open files from 4096 to 1048576
Mar 20 15:56:35 fredc named[2309]: found 32 CPUs, using 32 worker threads
Mar 20 15:56:35 fredc named[2309]: using 31 UDP listeners per interface
Mar 20 15:56:35 fredc named[2309]: using up to 4096 sockets
Mar 20 15:56:35 fredc named[2309]: loading configuration from ‘/etc/named.conf’
Mar 20 15:56:35 fredc named[2309]: using default UDP/IPv4 port range: [32768, 60999]
Mar 20 15:56:35 fredc named[2309]: using default UDP/IPv6 port range: [32768, 60999]
Mar 20 15:56:35 fredc named[2309]: listening on IPv6 interfaces, port 53
Mar 20 15:56:35 fredc named[2309]: listening on IPv4 interface lo, 127.0.0.1#53
Mar 20 15:56:35 fredc named[2309]: listening on IPv4 interface bond0, 192.168.0.2#53
Mar 20 15:56:35 fredc named[2309]: generating session key for dynamic DNS
Mar 20 15:56:35 fredc named[2309]: sizing zone task pool based on 6 zones
Mar 20 15:56:35 fredc named[2309]: set up managed keys zone for view _default, file ‘/var/lib/named/dyn//managed-keys.bind’
<automatic empty zone entries deleted>
Mar 20 15:56:35 fredc named[2309]: configuring command channel from ‘/etc/rndc.key’
Mar 20 15:56:35 fredc named[2309]: command channel listening on 127.0.0.1#953
Mar 20 15:56:35 fredc named[2309]: configuring command channel from ‘/etc/rndc.key’
Mar 20 15:56:35 fredc named[2309]: couldn’t add command channel ::1#953: address not available
Mar 20 15:56:35 fredc named[1943]: Starting name server BIND …done
Mar 20 15:56:35 fredc systemd[1]: Started LSB: Domain Name System (DNS) server, named.

tsu2 · March 22, 2017, 12:36am

First,
You should always post “code” ie commands and results
In the CODE tags (the hash button if you’re using the Forums web tool to create your post)

In any case,
Based on what you posted…
I highly doubt you’re using the YAST tool to configure your DNS…

Your named.service appears to be running fine
Don’t know why, but your service appears to be bound only to your localhost address (127.0.0.1) on port 953. The default DNS port is 53, and of course if the service isn’t bound to an external network interface, it’s not going to be seen by any other machine.
Although not in your systemctl status readout, it looks like your service <might> be bound to 127.0.0.2 port 53, but of course that’s also a localhost address so isn’t much use.

Recommendation:
If you don’t know how to set up DNS manually and even if you might,
Use the YAST DNS module to configure.

TSU

jwoodring · March 23, 2017, 2:26pm

Just to further clarify. My DNS configuration is correct and working fine. My question is, by going into Yast (DHCP as an example), my DNS startup is broken. The configuration is fine, the service is basically disabled and not set to start at boot. If I go back into DNS and re-start the service and tell it to start at boot, it works fine - including restarts of the system.

Does anyone know if Yast is broken regarding the named configuration?

Thank you.

tsu2 · March 23, 2017, 2:49pm

What do you mean by this?
Exactly, what steps did you do? - Did you use systemctl commands, or a YAST tool, or something else?

TSU

jwoodring · March 23, 2017, 2:55pm

Thank you for the quick replies…

I can re-enable the DNS by using Yast, systemctl, and even chkconfig. Any of these seem to work. I believe that when I go into Yast DHCP, it disables DNS but when I am “finished”, DNS isn’t re-enabled and whatever Yast does when it is exiting from the DHCP Server function, is breaking the DNS startup.

I am guessing that it might have something to do with the fact that named is legacy sysV and not systemd - but that’s just a guess.

Thank you!

jwoodring · March 23, 2017, 4:04pm

Here is the YaST log starting from when the “Finished” button is clicked in DHCP Server. You can see that Yast stops the named service (@ 2017-03-23 09:40:10) and then “decides” to disable the service (@2017-03-23 09:40:12) and that’s it.

Hope I got the CODE tags right this time…

2017-03-23 09:40:08 <1> fredc(6191) [Ruby] ui/service_status.rb:99 Input not handled by ServiceStatus: next
2017-03-23 09:40:08 <1> fredc(6191) [Ruby] dhcp-server/dialogs.rb:47 Running write dialog
2017-03-23 09:40:08 <1> fredc(6191) [Ruby] modules/Progress.rb:344 Progress::New(Saving DHCP Server Configuration, 4, "Write DHCP server settings", "Write firewall settings", "Restart DHCP server", "Write DNS server settings"])
2017-03-23 09:40:08 <1> fredc(6191) [Ruby] network/susefirewall2.rb:1461 Removing 'service:dhcp-server' from 'EXT' zone
2017-03-23 09:40:08 <1> fredc(6191) [Ruby] network/susefirewall2.rb:1454 Adding 'service:dhcp-server' into 'EXT' zone
2017-03-23 09:40:08 <1> fredc(6191) [Ruby] network/susefirewall2.rb:2464 Some ServicesAcceptRelated are defined
2017-03-23 09:40:08 <1> fredc(6191) [Ruby] network/susefirewall2.rb:1730 Firewall configuration has been changed. Writing: 
.
.
.
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show SuSEfirewall2.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl stop SuSEfirewall2.service `
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show SuSEfirewall2.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] network/susefirewall.rb:148 Stopped
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] network/susefirewall2.rb:1666 Starting firewall services
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] modules/Service.rb:140 Starting service 'SuSEfirewall2'
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show SuSEfirewall2.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl start SuSEfirewall2.service `
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show SuSEfirewall2.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] network/susefirewall.rb:131 Started
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DhcpServer.pm(DhcpServer::Write):1752 Enabling the DHCP service
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] modules/Service.rb:112 Enabling service 'dhcpd'
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show dhcpd.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl enable dhcpd.service `
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show dhcpd.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:09 <1> fredc(6191) [Ruby] modules/DnsServerHelperFunctions.rb:188 Regenerating zone 0.168.192.in-addr.arpa from zone forensic.local
2017-03-23 09:40:09 <1> fredc(6191) -e] New serial 2017032300
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::SelectZone):662 Selected zone with index 0
2017-03-23 09:40:09 <1> fredc(6191) -e] New serial 2017032304
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::SelectZone):662 Selected zone with index 1
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::GetConfigurationStat):960 Stat of the file '/etc/named.conf' is 'rights: 644, blocks: 16, size: 5243, owner: 0:0 changed: 1490279247, modifyied: 1490279247'
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::SaveGlobals):499 Wrote NETCONFIG_DNS_STATIC_SERVERS: 127.0.0.1 192.168.0.1
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::AdaptDDNS):388 INCLUDES: 
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::LdapStore):2120 LdapStore: not using ldap
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::LdapStore):2125 Writing reload scripts: 'createNamedConfInclude'
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::ZoneWrite):159 Skipping zone forensic.local, wasn't modified
2017-03-23 09:40:09 <1> fredc(6191) -e] New serial 2017032300
2017-03-23 09:40:09 <1> fredc(6460) [ag_dns_zone] Writing zone file /var/lib/named/master/0.168.192.in-addr.arpa
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::update_forwarding):1294 User-defined forwarder: resolver, using 'bind' for a while to update forwarders.conf
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::SetLocalForwarder):909 New local forwarder: bind
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::write_local_forwarder):1268 Current dns forwarder: bind
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::write_local_forwarder):1272 Updating forwarders by netconfig
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::update_forwarding):1301 Returning back to user-defined forwarder: resolver
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::SetLocalForwarder):909 New local forwarder: resolver
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::write_local_forwarder):1268 Current dns forwarder: resolver
2017-03-23 09:40:09 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::write_local_forwarder):1272 Updating forwarders by netconfig
2017-03-23 09:40:10 <1> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::Write):1559 Stopping service 'named'
2017-03-23 09:40:10 <1> fredc(6191) [Ruby] modules/Service.rb:182 Stopping service 'named'
2017-03-23 09:40:10 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show named.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:10 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl stop named.service `
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show named.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:12 <2> fredc(6191) [Perl] modules/DnsServer.pm(DnsServer::Write):1563 Local forwarder set to: resolver
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] modules/Service.rb:126 Disabling service 'named'
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show named.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl disable named.service `
2017-03-23 09:40:12 <3> fredc(6191) [bash] ShellCommand.cc(shellcommand):78 named.service is not a native service, redirecting to systemd-sysv-install
2017-03-23 09:40:12 <3> fredc(6191) [bash] ShellCommand.cc(shellcommand):78 Executing /usr/lib/systemd/systemd-sysv-install disable named
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show named.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] network/susefirewall2.rb:2464 Some ServicesAcceptRelated are defined
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] network/susefirewall2.rb:1730 Firewall configuration has been changed. Writing: $"FW_ALLOW_FW_BROADCAST_DMZ":"no", "FW_ALLOW_FW_BROADCAST_EXT":"no", "FW_ALLOW_FW_BROADCAST_INT":"no", "FW_BOOT_FULL_INIT":"no", "FW_CONFIGURATIONS_DMZ":"", "FW_CONFIGURATIONS_EXT":"apache2 apache2-ssl bind dhcp-server netbios-server ntp samba-client samba-server smtp sshd tftp vnc-httpd vnc-server xdmcp", "FW_CONFIGURATIONS_INT":"", "FW_DEV_DMZ":"", "FW_DEV_EXT":"bond0 br0 eth0 eth1", "FW_DEV_INT":"", "FW_FORWARD_ALWAYS_INOUT_DEV":"", "FW_FORWARD_MASQ":"", "FW_IGNORE_FW_BROADCAST_DMZ":"no", "FW_IGNORE_FW_BROADCAST_EXT":"yes", "FW_IGNORE_FW_BROADCAST_INT":"no", "FW_IPSEC_TRUST":"no", "FW_LOAD_MODULES":"nf_conntrack_netbios_ns", "FW_LOG_ACCEPT_ALL":"no", "FW_LOG_ACCEPT_CRIT":"yes", "FW_LOG_DROP_ALL":"no", "FW_LOG_DROP_CRIT":"yes", "FW_MASQUERADE":"no", "FW_PROTECT_FROM_INT":"no", "FW_ROUTE":"no", "FW_SERVICES_ACCEPT_DMZ":"", "FW_SERVICES_ACCEPT_EXT":"", "FW_SERVICES_ACCEPT_INT":"", "FW_SERVICES_ACCEPT_RELATED_DMZ":"", "FW_SERVICES_ACCEPT_RELATED_EXT":"", "FW_SERVICES_ACCEPT_RELATED_INT":"", "FW_SERVICES_DMZ_IP":"", "FW_SERVICES_DMZ_RPC":"", "FW_SERVICES_DMZ_TCP":"", "FW_SERVICES_DMZ_UDP":"", "FW_SERVICES_EXT_IP":"", "FW_SERVICES_EXT_RPC":"", "FW_SERVICES_EXT_TCP":"123 3817 69", "FW_SERVICES_EXT_UDP":"123 3817 69", "FW_SERVICES_INT_IP":"", "FW_SERVICES_INT_RPC":"", "FW_SERVICES_INT_TCP":"", "FW_SERVICES_INT_UDP":"", "FW_STOP_KEEP_ROUTING_STATE":"no", "enable_firewall":true, "start_firewall":true].
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] network/susefirewall2.rb:1750 Enabling firewall services
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] modules/Service.rb:112 Enabling service 'SuSEfirewall2'
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show SuSEfirewall2.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl enable SuSEfirewall2.service `
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show SuSEfirewall2.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] network/susefirewall.rb:211 Checking firewall status...
2017-03-23 09:40:12 <2> fredc(6191) [Ruby] modules/Service.rb:448 [DEPRECATION] `Status' in "/usr/share/YaST2/lib/network/susefirewall.rb:212:in `IsStarted'" is deprecated; use `active?` instead
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show SuSEfirewall2.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] network/susefirewall.rb:213 Firewall service is started
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] network/susefirewall2.rb:1664 Stopping firewall services
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] modules/Service.rb:182 Stopping service 'SuSEfirewall2'
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show SuSEfirewall2.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl stop SuSEfirewall2.service `
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show SuSEfirewall2.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] network/susefirewall.rb:148 Stopped
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] network/susefirewall2.rb:1666 Starting firewall services
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] modules/Service.rb:140 Starting service 'SuSEfirewall2'
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show SuSEfirewall2.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:12 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl start SuSEfirewall2.service `
2017-03-23 09:40:13 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show SuSEfirewall2.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:13 <1> fredc(6191) [Ruby] network/susefirewall.rb:131 Started
2017-03-23 09:40:13 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl try-restart dhcpd.service `
2017-03-23 09:40:13 <1> fredc(6191) [Ruby] yast2/systemd_unit.rb:122 `systemctl show dhcpd.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath `
2017-03-23 09:40:13 <1> fredc(6191) [Ruby] clients/dhcp-server.rb:30 Dhcp-server module finished
2017-03-23 09:40:13 <1> fredc(6191) [Ruby] clients/dhcp-server.rb:31 ----------------------------------------
2017-03-23 09:40:13 <1> fredc(6191) [liby2] genericfrontend.cc(main):820 Finished YaST2 component 'y2base'
2017-03-23 09:40:13 <1> fredc(6191) [liby2] genericfrontend.cc(main):825 Exiting with client return value 'true'
2017-03-23 09:40:13 <2> fredc(6191) [qt-ui] YQUI.cc(qMessageHandler):731 <libqt-warning> QObject::~QObject: Timers cannot be stopped from another thread
2017-03-23 09:40:13 <1> fredc(6191) [Y2Ruby] binary/YRuby.cc(~YRuby):117 Shutting down ruby interpreter.
2017-03-23 09:40:13 <1> fredc(6191) [Y2Perl] YPerl.cc(destroy):164 Shutting down embedded Perl interpreter.

tsu2 · March 24, 2017, 5:04pm

Are you using default settings?
For instance, DNS and DHCP integration normally is done only when those services are deployed as a part of Network Security like LDAP or Active Directory (At least AFAIK, I don’t know any other useful scenario).
And, I don’t know if it’s normal that in your latest log posting, there are entries which inspect the possibility of connecting to LDAP, then finding that no ldap store is found.

Ordinarily, unless you configure DNS and DHCP integration the services are completely separate, do not share any data and operate completely independently.
Even when integrated though, unless something has changed I only know that data is exchanged and the services still operate independently.

TSU