|
|
 |  |
Re: Primary/Slave IssueFrom: Men & Mice Support Date: Friday, March 26, 2004
Time: 3:35:29 pmThis is a consequence of your setup. In QuickDNS 3.5.x, QuickDNS
Remote on the slave server would tell the server to update whenever
the zone was changed. In QuickDNS 4.x, we rely on the DNS Notify
mechanism.
- QuickDNS Server for Mac OS 9 doesn't support DNS Notify.
- Since the two servers are managed separately, QuickDNS doesn't tell
the slave to update.
Therefore, the only way that the slave server updates is using the
old scheduled refresh mechanism, which is controlled by the Refresh,
Retry, Expire, and Serial entries in the SOA record at the top of
each zone. Basically, on a set schedule, the slave server checks in
with the master server to see if a change has been made.
To work around this, you can manually cause the slave to update.
Select the slave zone in the Manager window in QuickDNS Manager 4.x,
open the contextual menu, and select Reload.
____________________________________________________________________
Chris Buxton Men & Mice
Customer Support Specialist Making DNS Easy
At 2:26 PM -0800 3/26/04, Patrick Windmiller wrote:
>I have a primary server running on QDNS 3.5.3 on OS 9 and a secondary server
>running QDNS 4.6.x on 10.3.x Server. The problem I'm having is when I make
>changes to the primary server they are no longer changing on the secondary.
>And I can manually make the changes since the secondary is locked. How do I
>fix this?
>
>Thanks,
>
>Patrick
|

Return to Digital Point Solutions' Home Page |