BIND (named) does not listen for remote rndc after boot

Solution Verified - Updated -

Issue

  • The named daemon does not listen or respond to remote rndc calls after reboot.
  • It starts working after running rndc reload or systemctl restart named locally.
  • Error similar to the following is logged on start:

    Oct 04 08:22:13 server.example.com named[<PID>]: /etc/named.conf:123: couldn't add command channel 192.0.2.123#953: address not available
    

Environment

  • Red Hat Enterprise Linux 8
  • bind installed

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content