Comment 9 for bug 1683047

Just a me-too on 2.3.6.

 systemctl status bind9
● bind9.service - BIND Domain Name Server
   Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
  Drop-In: /run/systemd/generator/bind9.service.d
           └─50-insserv.conf-$named.conf
   Active: failed (Result: exit-code) since Mon 2019-09-09 03:21:53 UTC; 6s ago
     Docs: man:named(8)
  Process: 44098 ExecStop=/usr/sbin/rndc stop (code=exited, status=1/FAILURE)
  Process: 44036 ExecStart=/usr/sbin/named -f $OPTIONS (code=exited, status=1/FAILURE)
 Main PID: 44036 (code=exited, status=1/FAILURE)

Sep 09 03:21:53 pnjostkinfr02 named[44036]: using up to 4096 sockets
Sep 09 03:21:53 pnjostkinfr02 named[44036]: loading configuration from '/etc/bind/named.conf'
Sep 09 03:21:53 pnjostkinfr02 named[44036]: /etc/bind/maas/named.conf.maas:84: zone 'abc.243.10.in-addr.arpa': already exists previous definition: /etc/bind/maas/named.conf.maas:20
Sep 09 03:21:53 pnjostkinfr02 named[44036]: /etc/bind/maas/named.conf.maas:88: zone 'abd.243.10.in-addr.arpa': already exists previous definition: /etc/bind/maas/named.conf.maas:24
Sep 09 03:21:53 pnjostkinfr02 named[44036]: loading configuration: failure
Sep 09 03:21:53 pnjostkinfr02 systemd[1]: bind9.service: Main process exited, code=exited, status=1/FAILURE
Sep 09 03:21:53 pnjostkinfr02 rndc[44098]: rndc: connect failed: 127.0.0.1#953: connection refused
Sep 09 03:21:53 pnjostkinfr02 systemd[1]: bind9.service: Control process exited, code=exited status=1
Sep 09 03:21:53 pnjostkinfr02 systemd[1]: bind9.service: Unit entered failed state.
Sep 09 03:21:53 pnjostkinfr02 systemd[1]: bind9.service: Failed with result 'exit-code'.