Date: Wed, 06 Jul 2005 14:38:21 -0400 From: "Simon" <simon@optinet.com> To: "freebsd-isp@freebsd.org" <freebsd-isp@freebsd.org>, "John Von Essen" <john@essenz.com> Subject: Re: rndc reload and BIND9 Message-ID: <20050706183443.0C73843D48@mx1.FreeBSD.org> In-Reply-To: <20050706105612.W22721@beck.quonix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, reload is graceful, it will only load named.conf and new zones, it will not touch preloaded zones. Having 2 masters makes no sense, unless you are actually splitting the zone files between them. Unless you perform a cold start of your bind, transfers only occur when a serial number is updated (upon reload) or when a zone expires. -Simon On Wed, 6 Jul 2005 11:02:04 -0400 (EDT), John Von Essen wrote: > >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 >_______________________________________________ >freebsd-isp@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-isp >To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050706183443.0C73843D48>