|
|
 |  |
Re: Primary/Slave IssueFrom: Men & Mice Support Date: Saturday, April 10, 2004
Time: 11:54:59 amAt 10:11 AM -0700 4/10/04, Warren Michelsen wrote:
>At 2:15 PM -0800 3/25/04, Men & Mice Support wrote:
>>Sorry for the long delay.
>>
>>Having one server as master (primary) and one as slave is the
>>normal way things work. It doesn't sound like you have a problem in
>>your configuration.
>
>In the past, all my zones were in the Primary data folder on both
>servers and when I updated via QDNS, it updated both at once, since
>I was connected to both when the changes were made.
Right, in 3.5.1, this works, though you won't be able to create
further zones in this way. This is not the best way to do things.
>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).
In later versions, the only benefit to connecting to a slave server
is when creating or deleting zones, since the DNS Notify mechanism
takes care of making sure the slave servers get the update.
>In any case, I copied the primary data file to the second server
>(deleting the secondary entry for that zone) and now things appear
>to be working as they used to.
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.
____________________________________________________________________
Chris Buxton Men & Mice
Customer Support Specialist Making DNS Easy
|

Return to Digital Point Solutions' Home Page |