rndc and Bind 9

[Lisa Burke]

Jim -

Thanks for the info.  I just got this to work.  I had to actually stop the
named instance (by killing the pid) then restarted it.  After doing that I
was able to utilize the rndc reload.  I had not actually stop/started named
after adding the key statements, files.  Had, instead simply started to try
to restart with rndc.  

Thanks again.

Lisa

-----Original Message-----
From: Jim Reid [mailto:jim at rfc1035.com]
Sent: Tuesday, December 12, 2000 11:47 AM
To: Lisa Burke
Cc: bind-users at isc.org
Subject: Re: rndc and Bind 9 


>>>>> "Lisa" == Lisa Burke <lburke at once.com> writes:

    Lisa> I meant to say: "There are no named error messages in
    Lisa> /var/adm/messages".  There are actually messages about it
    Lisa> starting successfully.  Excuse my mis-statement.  I also
    Lisa> added port 953 tcp and udp to /etc/services (just to see)
    Lisa> and I still get "connection refused".  I'll try lsof as you
    Lisa> suggest.  Is it anything like snoop?

I don't think so. IIRC snoop is a Sun tool for looking at network
traffic. I believe snoop is like tcpdump but not as useful. lsof is a
*great* PD tool for finding out which files/sockets a process is using
or for finding out which processes are using some files or sockets. It
can also tell you about the shared executables and libraries and
current working directory of a process.

As I said before the "connection refused" messages mean that the name
server hasn't created the listener on port 953 for rndc to connect to.
That tends to suggest you're running a name server that doesn't know
anything about this control socket. Are you *sure* you're running a
BIND9 server? Does lsof confirm this? Is that BIND9 server reading the
named.conf file you posted earlier? What is in the name server logs?
Why didn't you post them here? Your problem could be diagnosed and
fixed a lot quicker if you gave that information.