On 22/04/2021 02:39, Jack Craig wrote:
Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: zone localhost.localdomain/IN: has 0 SOA records Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: zone localhost.localdomain/IN: has no NS records Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: zone localhost.localdomain/IN: not loaded due to errors. Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: _default/localhost.localdomain/IN: bad zone Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: zone localhost/IN: has 0 SOA records Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: zone localhost/IN: has no NS records Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: zone localhost/IN: not loaded due to errors. Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: _default/localhost/IN: bad zone Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: has 0 SOA records Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: has no NS records Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: not loaded due to errors. Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: _default/1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: bad zone Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: zone 1.0.0.127.in-addr.arpa/IN: has 0 SOA records Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: zone 1.0.0.127.in-addr.arpa/IN: has no NS records Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: zone 1.0.0.127.in-addr.arpa/IN: not loaded due to errors. Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: _default/1.0.0.127.in-addr.arpa/IN: bad zone Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> bash[1451129]: zone 0.in-addr.arpa/IN: loaded serial 0 Apr 21 11:36:07 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> systemd[1]: named.service: Control process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel <https://lists.freedesktop.org/mailman/listinfo/systemd-devel> i just swapped the provided file to /etc/named.conf and restarted, thoughts?
None of this makes any sense. I ran the named.conf file on 2 systems after just doing "dnf install bind". No problems. Lets's confirm a few things. 1. What version of Fedora are you running? I'm testing on F33. 2. What version of bind? I'm at bind-9.11.28-1.fc33.x86_64 3. Have you changed the files in /var/named? named.ca named.empty named.localhost named.loopback Those are the config files that should be loaded. And finally. the output of systemctl status named -- Remind me to ignore comments which aren't germane to the thread. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
