rndc reload and BIND9
From: John Von Essen (john_at_essenz.com)
Date: 07/06/05
- Previous message: John Von Essen: "Re: Multiple IP MRTG or Similar"
- In reply to: Lewis Watson: "Re: Multiple IP MRTG or Similar"
- Next in thread: Jett Tayer: "Re: rndc reload and BIND9"
- Reply: Jett Tayer: "Re: rndc reload and BIND9"
- Reply: Matthew D. Fuller: "Re: rndc reload and BIND9"
- Reply: Simon: "Re: rndc reload and BIND9"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 6 Jul 2005 11:02:04 -0400 (EDT) To: freebsd-isp@freebsd.org
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"
- Previous message: John Von Essen: "Re: Multiple IP MRTG or Similar"
- In reply to: Lewis Watson: "Re: Multiple IP MRTG or Similar"
- Next in thread: Jett Tayer: "Re: rndc reload and BIND9"
- Reply: Jett Tayer: "Re: rndc reload and BIND9"
- Reply: Matthew D. Fuller: "Re: rndc reload and BIND9"
- Reply: Simon: "Re: rndc reload and BIND9"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|