DNS Changes only apply when i restart named

[razR]

Hi There,

This is my first time using cPanel/WHM and i like it very much, however when i add a (sub)domain to my server i need to restart NAMED manually before it actually applies.

When i add a (sub)domain (example: google.nl) and i PING it on the webserver itself it says:

ping google.nl
ping: unknown host google.nl

And when i do 'service named restart' it resolves perfectly.


However also when i stop CSF & Iptables it updates it again but it doesnt help always.

[razR]

Nobody knows a solution? I'm getting tired to manually reload NAMED every time there is an DNS change occoured.

[razR]

UPDATE
When i do the fixndc command i get the following

 /usr/sbin/rndc status failed: WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf)rndc: connect failed: 127.0.0.1#953: connection refused

\

and

Error reloading bind on web: rndc: connect failed: 127.0.0.1#953: connection refused

[cPanelMichael]

Hello

The most important error message in this case is:

Error reloading bind on web: rndc: connect failed: 127.0.0.1#953: connection refused

There are several potential causes of this error. Feel free to submit a ticket so we can take a closer look:

Submit A Ticket

You can post the ticket number here, and we can update this thread with the exact cause of the problem after the issue is resolved.

Thank you.

[radeonpower]

I had this problem few days ago.

rndc failed to start until I disabled/stopped the 'portreserve' service. You might also need to delete the /etc/named.conf.cache file, new one will be generated automaticly.

[cPanelMichael]

I had this problem few days ago.

rndc failed to start until I disabled/stopped the 'portreserve' service. You might also need to delete the /etc/named.conf.cache file, new one will be generated automaticly.

If you would like to determine if that's the cause of this issue, please post the output of the following command:

# grep portrelease /etc/init.d/named

Depending on the version of CentOS you are using, you should see output such as:

 [ -x /sbin/portrelease ] && /sbin/portrelease named &>/dev/null || :

Thank you.

[radeonpower]

I'm using CentOS 6.3 and this command did not output anything.

root@ns3 [~]# grep portrelease /etc/init.d/named
root@ns3 [~]#

The problem stopped anyway after I stopped portreserve. :P

Funny enough though, I have few servers, some of them have this output and some dont.

[cPanelMichael]

I'm using CentOS 6.3 and this command did not output anything.

root@ns3 [~]# grep portrelease /etc/init.d/named
root@ns3 [~]#

If you are using CentOS 6.3, you can run the following commands to resolve this issue:

# mv /etc/init.d/named /etc/init.d/named.bak
# yum reinstall bind

You should then see the expected output when running:

# grep portrelease /etc/init.d/named

Example output should be:

[ -x /sbin/portrelease ] && /sbin/portrelease named &>/dev/null || :

If you see this output, you can then run:

# /etc/init.d/named stop; /etc/init.d/portreserve restart; /etc/init.d/named start; netstat -plan | grep 953 | grep named

This should resolve the issue, and you should no longer receive connection refused errors when reloading rndc.

Thank you.

[razR]

Reinstalling BIND worked, thanks for the help

[ceylon]

Got the same error on fresh installation of the CLOUDLINUX 6.3 x86_64 xenhvm
Re-installed the system. But same error.

Only resolve after re-installing bind.

Thanks for the help and its really helpful.