Skip to main content

Error reloading bind on ns2: rndc: 'reload' failed: failure

Comments

3 comments

  • craigedmonds
    Hi, I am noticing this on other domains now and also on one of my other cpanel servers, so must be a cpanel issue I think. Anyone know how to solve this? [QUOTE]Bind reloading on maggie using rndc zone: [birlasoft-westbrook-alliance.com] Bind reloading on ns1 using rndc zone: [birlasoft-westbrook-alliance.com] Bind reloading on ns1 using rndc Error reloading bind on ns1: rndc: 'reload' failed: failure Bind reloading on ns3 using rndc zone: [birlasoft-westbrook-alliance.com] Bind reloading on ns3 using rndc Error reloading bind on ns3: rndc: 'reload' failed: failure Bind reloading on ns4 using rndc zone: [birlasoft-westbrook-alliance.com] Bind reloading on ns4 using rndc Error reloading bind on ns4: rndc: 'reload' failed: failure Bind reloading on ns2 using rndc zone: [birlasoft-westbrook-alliance.com] Bind reloading on ns2 using rndc: rndc: 'reload' failed: failure Error reloading bind on ns2: rndc: 'reload' failed: failure
    0
  • craigedmonds
    [SOLVED] Re: Error reloading bind on ns2: rndc: 'reload' failed: failure I have solved the issue now (no thanks to anyone on cpanel.net I am afraid). I logged into ns1 (dns only server) and ran the following command [QUOTE]/etc/init.d/named restart
    This gave me this error: [QUOTE]Error in named configuration: /etc/named.conf:10693: zone 'someotherdomainname.com': already exists previous definition: /etc/named.conf:8581 /etc/named.conf:23122: zone 'someotherdomainname.com': already exists previous definition: /etc/named.conf:21010 FAILED
    This indicated there was a double entry of a zone file for someotherdomainname.com in /etc/named.conf. I then commented out the duplicate zone file entry like so: .vB Then I went back to the main cpanel server and tried to update a dns record and did not get any errors which was a good sign! I then did the same edit withthe /etc/named.conf on the other 3 nameservers... ns2 + ns3 + ns4 and everything was back to normal again. BTW, I did not have to restart BIND or anything at all, just commented the /etc/named.conf file and saved it. I do not know what caused this duplication issue but the above solution worked for me and I hope it saves someone else hours of troubleshooting.
    0
  • cPanelMichael
    Hello :) I am happy to hear you were able to resolve the issue. Thank you for sharing the solution with us. Note that you can also remove duplicate DNS Zones with a command such as: /scripts/cleandns
    Rebuilding the DNS configuration file would then ensure any duplicate entries are removed: /scripts/rebuilddnsconfig
    Thank you.
    0

Please sign in to leave a comment.