(1) I include the rndc.key file and have it readable only to named group
named. Then I don't have to worry about having the same secret in two
files. The rndc.conf file is only needed if you're going to do
something out of the ordinary, e.g., use rndc from a remote server.
[But see #3]
(2) I don
p...@mail.nsbeta.info wrote:
>
> I don't know what's the problem.
> Just copied the config files to another host and run bind master on
> it, everything works fine, including the zone transfer for multi-views.
> Thanks.
> p...@mail.nsbeta.info writes:
>>
>> And, the named version is:
>> # named -v
I don't know what's the problem.
Just copied the config files to another host and run bind master on it,
everything works fine, including the zone transfer for multi-views.
Thanks.
p...@mail.nsbeta.info writes:
And, the named version is:
# named -v
BIND 9.6.1-P2
I'm pretty sure t
RNDC is only allowed from localhost, so the only place these would work
would be from a command shell on the server that is the master. You did
not specify where you were running rndc.
Hello,
I'm running it in master.
Here is the -V output:
# rndc -V status
create memory context
create
RNDC is only allowed from localhost, so the only place these would work
would be from a command shell on the server that is the master. You did
not specify where you were running rndc.
I run it on master.
Here is the -V output:
# rndc -V status
create memory context
create socket manage
And, the named version is:
# named -v
BIND 9.6.1-P2
I'm pretty sure the secret in both named.conf and rndc.conf are the same.
Thanks.
p...@mail.nsbeta.info writes:
Hello gurus,
my rndc related commands in bind master with multi-views run fail,but in
slave it's running correctly.
Hello gurus,
my rndc related commands in bind master with multi-views run fail,but in
slave it's running correctly.
# rndc status
rndc: connection to remote host closed
This may indicate that
* the remote server is using an older version of the command protocol,
* this host is not authorize
7 matches
Mail list logo