BIND rndc problem

Kevin Darcy kcd at daimlerchrysler.com
Thu Aug 7 21:10:34 UTC 2003


Mike Kinzie wrote:

> hello,
> I have Redhat 8 with BIND 9.2.1
> rndc has stopped working and I cannot ping my domain or 127.0.01
> I have checked my /va/log/messages and found the following with regard to
> the named server startup on a reboot:
>
> -couldn't find rndc key for use with command channel: 127.0.0.1#953
> I have the following in named.conf:
>
> controls {
>         inet 127.0.0.1 allow { localhost; } keys { rndc_key; };
> };
>
> all the zone files loaded okay.
>
> I do not understand the command channel and how to correct the rndc failure.

The BIND 9 documentation tells how to set up rndc. Basically you need to
generate a key.

The failure to set up an rndc channel shouldn't have any direct relationship to
your inability to resolve names, though. Although it's encouraging that you are
looking in the log file for error messages (so many people forget that step) do
you have any other information about that problem beyond "I cannot ping my
domain or 127.0.01" and "all the zone files loaded okay"? Have you tried
querying the nameserver with a DNS lookup tool like "dig"? Is your machine even
configured to use DNS for name resolution? If you turn on query logging, do you
see the query attempts being logged? Does a "netstat" show anything listening
on port 53?


- Kevin





More information about the bind-users mailing list