I agree - we are removing 1/2 the masters in a couple weeks to help
things. Slaves only talk to masters, there are no slaves of slaves
as we refer to them. Our architecture goal has been uniformity among
the configurations, and this is part of the price we pay for that.
At a functional level,
On 2010/01/20, at 13:03, Dave Sparro wrote:
We would like to make this better.
Can anyone help with ideas on this? Are we missing something obvious?
In that situation I'd consider using CVS on all of the servers to maintain
the DNS data.
Just make all of the servers masters, and
serial-query-rate
While this appears to be helping in the lab, it's still taking between
2 and 3 minutes for each slave to even finish receiving the NOTIFYs
from the master. They then start hitting the master(s) with SOA
queries whch seems to take a really long time.
We're going to keep
On Wed, Jan 20, 2010 at 03:52:33PM -0500, Todd wrote:
serial-query-rate
While this appears to be helping in the lab, it's still taking between
2 and 3 minutes for each slave to even finish receiving the NOTIFYs
from the master. They then start hitting the master(s) with SOA
queries whch
Good day all,
We've run into a problem with our DNS servers. The way we update our
masters is via a CVS Checkout and reload of the zones modified.
Sometimes though, we need to reload the whole config for big
changs/etc. When that happens, all 6 masters (I know, we're getting
rid of some) send
On Mon, Jan 18, 2010 at 1:27 PM, Todd canada...@gmail.com wrote:
Good day all,
We've run into a problem with our DNS servers. The way we update our
masters is via a CVS Checkout and reload of the zones modified.
Sometimes though, we need to reload the whole config for big
changs/etc. When
In message 91aa34af1001181327q7f5de882vf47052ed39d87...@mail.gmail.com, Todd
writes:
Good day all,
We've run into a problem with our DNS servers. The way we update our
masters is via a CVS Checkout and reload of the zones modified.
Sometimes though, we need to reload the whole config for
7 matches
Mail list logo