Hugh E Cruickshank wrote:
> I can get around this by using "service named start" but I should not
> have to do this. Has anyone encountered something similar and can pass
> on some words of wisdom?
yes, don't use rndc the whole concept is stupid to begin with.
nate
On Thu, Nov 26, 2009 at 1:04 AM, Hugh E Cruickshank wrote:
> CentOS 4.8, BIND 9.2.4
> 3. Delete the journal files:
> rm *.jnl
why to do that?
you can do simple zone update by:
rndc freeze [zone]
if you got error like:
rndc: 'freeze' failed: not found
try than:
rndc freeze [zone] in internal
ed
On Wed, Nov 25, 2009 at 03:04:59PM -0800, Hugh E Cruickshank wrote:
> CentOS 4.8, BIND 9.2.4
>
> 1. Flush the cache buffers:
>
>rndc flush
>
> 2. Stop named:
>
>rndc stop
>
> 3. Delete the journal files:
>
>rm *.jnl
>
> 4. Edit the forward and/or reverse zone files as necessary.
Hello ,
I am facing same problem but with CentOS 5.4 and BIND 9.3.6 while I
was having 5.3 named was working fine but now it give me same error in
Service configuration panel to start named I have to reboot the system
but if I give Service named restart it stops and fails to start only I
can use s
CentOS 4.8, BIND 9.2.4
Hi All:
I have a rather annoying problem with rndc which I have not been able
to resolve despite much searching and many attempts to correct. When
making changes to our DNS entries I have tried to use the following
procedures:
1. Flush the cache buffers:
rndc flush
2.
5 matches
Mail list logo
