 |  |
At 1:05 PM -0500 9/8/01, Len Conrad wrote:
Re: Question about secondary zone updates...
From: Men & Mice Support
Date: Sunday, September 9, 2001
Time: 5:02:35 pm
>>Incidentally, Len, I've checked the logs of both servers, they are hosted =
on
>>two of our machines maintained by us. No errors, but no record of transfe=
r
>>activity either.
In the log, if the log level is set to at least "Normal" level, you
should see the following items in the log file of the slave server
for most refresh cycles:
Starting check for domain "zone.name."
Done checking SOA for domain "zone.name.", no update needed
Here's what you should see at the next refresh check after a zone has
been modified:
Starting check for domain "zone.name."
Attempting to download zone "zone.name." with serial number 123456,
from 192.168.1.1
Zone "zone.name." successfully downloaded
Loading domain "zone.name."
Of course, these log entries don't necessarily appear adjacent in
your log - it's quite possible for them to be separated by other log
entries.
If either the refresh check or zone transfer should fail, there will
be an error message in the log about that.
>dig @zonemaster domain.com soa
>
>are you getting 'aa' flag?
Since many of our users don't have direct access to a command line
host with the 'dig' command, another way to test this is with DNS
Expert's DNS Query tool.
Send a non-recursive query to your master server with the query name
set to the zone name, and the query type set to SOA. In the header
section, is the response marked as authoritative?
>>So if I set the REFRESH value to something much lower it should update
>>quicker.
>
>not as quick as NOTIFY
Ah, but QuickDNS Server for classic Mac OS doesn't support NOTIFY.
As of QuickDNS 3.0.1, however, QuickDNS does support its own "instant
update" feature - when the zone is saved, the master server is told
to read in the new version. 5 seconds later, the slave server(s)
is/are told to check the master for a new version (initiate a refresh
check). This is very similar to how NOTIFY works, though not
identical.
In older versions, the old-fashioned Refresh/Retry/Expire mechanism
handles all slave server updates.
Note also that, when you save a zone, unless you've manually modified
the serial number, the serial number will be automatically updated.
This ensures that the slave server will get the new version at its
next update check (which occurs very soon in the more recent
versions, as described above).
>> I guess back to my original question then, if setting this real
>>low, won't resources be tied up checking the slave zone more often?
>
>as I said, it=B4s only a single query from each slave to the master(s)
>for the SOA record. no sweat, even once per minute.
Right.
>>And again, back to my original post, is there a reason why QDNS defaults n=
ew
>>zones to 8 hour REFRESH values? Must be something there if QDNS thinks it
>>needs to be 8 hours.
It's an essentially arbitrary choice. We used the suggested values
from RFC 1537 as the defaults in QuickDNS.
<http://www.faqs.org/rfcs/rfc1537.html>
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!
Messages In This Thread:
Return to Digital Point Solutions' Home Page
| home | |
| products | |
| services | |
| support | |
| email lists |
| optigold isp | |
| optigold isp news | |
| home inspection | |
| inspectrix | |
| java companion | |
| oracle | |
| quickdns pro | |
| search engine | |
| veterinary |
| tips | |
| employees | |
| free tools | |
| portfolio | |
| jobs | |
| contact |
888/4-DPOINTSupport:
858/452-3696