Search Again:

Re: Primary/Slave Issue

From: Warren Michelsen
Date: Saturday, April 10, 2004
Time: 12:45:03 pm

At 11:53 AM -0700 4/10/04, Men & Mice Support wrote:
>At 10:11 AM -0700 4/10/04, Warren Michelsen wrote:
>
>>If I'm going to go the master/slave route, there's not much point in connecting to both with QDNS manager.
>
>Sure there is. If you don't connect to both, with QuickDNS 3.5.x, you end up waiting for the periodic refresh check before the slave server gets the update. If you do connect to both, then QuickDNS Manager will tell the slave server to get the new version right away (within a few seconds, anyway).
>
>Just so you know, later versions of QuickDNS will not behave the same way, updating both servers at once. QuickDNS is really designed for one server and zero or more slaves for each zone.

So the best thing to do is convert one of these to all slave zones, but still connect to it when adding, deleting or modifying zone data, correct?

I'd been thinking all along that, since it worked with all primary data on both servers, that's the way it was intended to work...




Messages In This Thread:



Return to Digital Point Solutions' Home Page