On Mar 16 2012, Mark Pettit wrote:
[...]
We have an antiquated push process that copies files into the zonefile
directory and then tells BIND rndc reload. For various reasons,
rndc reload takes about 120 seconds to complete. BIND is not answering
queries for a very large part of that time.
I've read carefully through the BIND ARM and am still not sure of the answer to
this, so I figured I'd ask on here.
rndc reconfig causes BIND to re-load its config file, but unlike rndc
reload, BIND will not scan the zone files it's mastering to see if there have
been any updates. This is
On 16/03/2012 09:10, Mark Pettit wrote:
Hi Mark,
However, I'm curious what I should do when an update contains both a
new config file and new zone files.
If you have *new* zones, rndc reconfig will also load them. You don't
need to run rndc reload for them when they are first added to the
On 3/16/2012 4:10 AM, Mark Pettit wrote:
I've read carefully through the BIND ARM and am still not sure of the answer to
this, so I figured I'd ask on here.
rndc reconfig causes BIND to re-load its config file, but unlike rndc
reload, BIND will not scan the zone files it's mastering to see
On 3/16/2012 4:10 AM, Mark Pettit wrote:
We have an antiquated push process that copies files into the
zonefile directory and then tells BIND rndc reload. For various
reasons, rndc reload takes about 120 seconds to complete. BIND is
not answering queries for a very large part of that time.
I was considering doing rndc reconfig, followed by a rndc reload
zone for each of the new zones.
Would this work?
'reconfig' reloads the configuration without reloading all of the zones,
but if it sees that you've added or removed any zones in the config file,
it will load or unload those.
6 matches
Mail list logo
