Date: Wed, 6 Jul 2005 11:02:04 -0400 (EDT) From: John Von Essen <john@essenz.com> To: freebsd-isp@freebsd.org Subject: rndc reload and BIND9 Message-ID: <20050706105612.W22721@beck.quonix.net> In-Reply-To: <06ef01c581f6$c54fb3c0$de0a0a0a@visionsix.com> References: <3b88b80a0507051933f4750f3@mail.gmail.com> <06ef01c581f6$c54fb3c0$de0a0a0a@visionsix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Following a post I had about BIND9, I need to verify a certain behavior with BIND9 and issuing a rndc reload. Instead, of having a master and slave, I am going to have two masters. One master is the real master, the other gets replicated via rsync. The main reason for this approach is to cut down on all the zone transfers (we have 12,000 domains). After every hourly rsync, I will issue a rndc reload. If anything has changed, named will see it with the new serial number. Does the reload keep dns functionality up and running while it performs the reload? A pure stop and start will take about 55 seconds, which isn't acceptable every hour. But if the reload (which appears to take 10 seconds) is gracefull and keep existing functionality intact while it reloads, then that would be great. Just need to verify. Thanks John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050706105612.W22721>