|
|
 |  |
Re: Forcing a Zone ReloadFrom: Men & Mice Support Date: Monday, October 7, 2002
Time: 3:49:01 pmActually, because DNS Notify may not always be available, QuickDNS
does the following:
- Save the zone to file on the master server.
- Tell the master server to reload the zone.
- Wait a few seconds.
- On each slave server, tell the server to reload the zone. This has
the effect of starting a refresh check on each slave. If DNS Notify
has already done its thing, then this is redundant.
____________________________________________________________________
Chris Buxton Men & Mice
support@menandmice.com Making DNS Easy
At 8:45 AM -0500 10/5/02, Len Conrad wrote:
>>Well I was actually wondering if there was a way through the QDNS Pro
>>interface. I actually reloaded directly on the box, but it would
>>be wonderful
>>if the QDNS Pro interface did this for me as I am using it to
>>manage the zones.
>> Or does QDNS Pro auto try to reload a modified zone when its saved
>>and in this
>>case it did not work and I had to hit the server manually?
>
>Well, it's early Saturday morning so I'm stepping in and guessing.
>I suspect that qdns is for managing the config and data files, NOT
>for replacing what BIND does well already. When a zone master is
>reloaded, then it should immediately push out a NOTIFY query to all
>zone slaves. If all conditions are met, then the slaves refresh
>the zone. I don't see what role QDNS would have in replacing those
>mechanisms.
>
>If the slaves are not refreshing, then I suspect some prerequisite
>is not in place.
>
>What are the names of these secret zones that don't refresh? If
>they are public zones, then there's no risk in telling us what they
>are so we can check them from our POV.
>
>Len
|

Return to Digital Point Solutions' Home Page |