These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for BIND DNS Server won't start on the new forum.
Hi, my Virtualmin won't start the BIND DNS Server. When I select the green arrow to start the BIND DNS Server, I receive the error: Failed to start service : Failed to start BIND : Redirecting to /bin/systemctl start named.service Job for named.service failed. See 'systemctl status named.service' and 'journalctl -xn' for details.
Howdy,
What BIND errors do you see in the logs when this occurs?
-Eric
Thank you for your reply. I went to $ /var/log/messages, but not sure if this is the correct path.
Howdy,
Which logs to review depends on your distro -- which distro is it that you're using there?
-Eric
Hello, I'm on CentOS Linux 7.0.1406. Virtualmin version: 4.10.gpl GPL.
Hello?
Yeah, /var/log/messages is the place where BIND related error/notification messages should show up.
I don't see any BIND related notices though in your output above.
Are you looking at the end of that logfile, right after attempting to restart BIND? What you'd be looking for are log messages for the service with the name "named".
-Eric
Well I don't think all the text displayed in the /var/log/messages file, but here is what was able to be copied.
Virtualmin forum not posting reply with code results above?
I have now followed https://www.virtualmin.com/documentation/dns/faq but the Virtualmin > System Settings > Server Templates > Default Settings > Edit template section: BIND DNS domain > Master DNS server hostname > Hostname: > Additional manually configured nameservers: ns1.domain.com and ns2.domain.com > unable to save the settings?
Howdy,
What happens when trying to save the settings? If you're receiving an error, what error is it giving you?
-Eric
The error is: Failed to save server template: Additional nameserver ns1.domain.com does not exist.
I don't know if adding these details are needed or it's a wild goose chase, but that's the error when I enter in the details.
If anyone's reading this, there is some kind of incompatibility in the DNS when restoring backups. The fix is to doisable DNS for the domain in virtual server settings and then re-enable it. This regenerates the zone file for the domain and you can then start BIND succcessfully.
Delete any views or client view from the config file : /etc/named.conf