DNS Server not working

alcngz

• September 13, 2018 04:49

Hello, -------------------- Note: xxxx (hidden domain) Problem Details: [2018-09-13 09:38:49 +0000] info [restartsrv_bind] systemd failed to start the service "named" (The "/usr/bin/systemctl restart named.service --no-ask-password" command (process 6977) reported error number 1 when it ended.): Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details. [2018-09-13 09:38:54 +0000] info [restartsrv_bind] systemd failed to start the service "named" (The "/usr/bin/systemctl restart named.service --no-ask-password" command (process 6988) reported error number 1 when it ended.): Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details. Waiting for "named" to start ""failed. Cpanel::Exception::Services::StartError Service Status Service Error (XID 9xm9y8) The "named" service failed to start. Startup Log Sep 13 09:38:54 server.xxxxxxxxxxxxxxxxxx.com systemd[1]: Starting Berkeley Internet Name Domain (DNS)... Sep 13 09:38:54 server.xxxxxxxxxxxxxxxxxx.com bash[6993]: /etc/named.conf:1: unknown option 'version' Sep 13 09:38:54 server.xxxxxxxxxxxxxxxxxx.com bash[6993]: /etc/named.conf:2: unknown option 'hostname' Sep 13 09:38:54 server.xxxxxxxxxxxxxxxxxx.com systemd[1]: named.service: control process exited, code=exited status=1 Sep 13 09:38:54 server.xxxxxxxxxxxxxxxxxx.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). Sep 13 09:38:54 server.xxxxxxxxxxxxxxxxxx.com systemd[1]: Unit named.service entered failed state. Sep 13 09:38:54 server.xxxxxxxxxxxxxxxxxx.com systemd[1]: named.service failed. named has failed. Contact your system administrator if the service does not automagically recover. -------------------- Website is not working.

• 

  dalem

  • September 13, 2018 11:59

  lines in /etc/named.conf are incorrect /etc/named.conf:1: unknown option 'version' /etc/named.conf:2: unknown option 'hostname'

  0
• 

  cPanelLauren

  • September 14, 2018 15:45

  Hello @alcngz As indicated above the lines: Sep 13 09:38:54 server.xxxxxxxxxxxxxxxxxx.com bash[6993]: /etc/named.conf:1: unknown option 'version' Sep 13 09:38:54 server.xxxxxxxxxxxxxxxxxx.com bash[6993]: /etc/named.conf:2: unknown option 'hostname'
  I would suggest running the following: /scripts/rebuilddnsconfig
  Please let us know if this resolves the issue for you. Thanks!

  0
• 

  SactoBob

  • September 18, 2019 11:37

  FYI. Just in case. Reporting similar issue. All 3 of my DNS-Only servers were failing. It was also a config issue, an entry that was in both internal/external and startup was complaining about this config line was already in use. This config has been running fine for months. named update? I removed the line (an include of slave domains) from internal and named restarted. Of course now internal look-ups for a hand full of domains fail, but they work for remote look-ups and named starts, something I'll need to look at further at a reasonable time (2am here)... Edit: So my issue was different, but still a start error. My DNS-Only servers also act as slaves to a few domains, so I'm loading a slave config file in the Internal and External sections of named.conf. However, the 2nd load fails with an error that the slave files are already opened. Why this works for all the other internal/external files in the config but not the slave ones is a mystery to me and this config has been running since Jan 2019. This error comes up in google search too of "named writable file already in use" and using the info found I changed the External slaves configs to use "in-view internal" and named now starts and responds to the slaves properly.

  0

Please sign in to leave a comment.