rndc stops listening

John Thurston john.thurston at alaska.gov
Fri Dec 11 20:13:34 UTC 2020

Running BIND 9.16.9 on CentOS 8

I have the following in my .conf
> controls {
>   inet port 953
>     allow {; } keys { "mykey"; };
>   inet port 953
>     allow {;; }
>     keys { "threekey"; "fourkey"; };
> };

And I normally can see the named process is listening on tcp:953 on both and   But sometimes later, I find it listening only 
on   If I do an 'rndc reconfig', it starts listening again on 
both addresses. Normal DNS service has continued uninterrupted.

I can't find footprints left from anything falling down. I'd could just 
install a watchdog to 'reconfig' whenever port 953 stops answering, but 
I'd rather figure out why it is stopping and correct the problem. To do 
that, I need more information.

Am I not looking in the correct log?
Do I need to crank up the logging level for something?
If so, for what? and how high?

Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska

More information about the bind-users mailing list