dear dns gurus,
can someone please give me a short explanation about the difference from a
zone transfer to the reload of a zone in w2k3 dns environment.

thank you very much
tim

Each primary and secondary zone of the same name on two separate DNS servers
contains a serial number. Peroidically a check is made to determine if the
serial number of the primary matches the secondary. If they do, nothing
happens. If they don't then the secondary zone is locked and the secondary
zone gets the changes (i.e. adds, deletes and changes) to the zone. Note
that I said changes as this makes the update process quicker. This process
repeats over and over again day after day.

A reload from master is a manual process kicked off by executing a
DNSCMD.EXE command line request or by requesting the process though the DNS
Managment Console on the server performing your DNS functions. When such a
request is made the secondary copy get a full and complete reload of the
zone from the primary without regard to the serial numbers or the time.
Reloads can be done whenever and however frequently you want.

A reload of the Primary zone is typically performed from the Managment
Console. When you invoke the console and display a zone the records in the
zone are cached. When you request a reload you are asking that the cache be
completely replaced.


"Tim Moor" <(E-Mail Removed)> wrote in message
news:4432edf5$(E-Mail Removed)...
> dear dns gurus,
> can someone please give me a short explanation about the difference from a
> zone transfer to the reload of a zone in w2k3 dns environment.
>
> thank you very much
> tim
>
>
>

thank you very much for your information. one more question:

> Peroidically a check is made to determine if the serial number of the
> primary matches the secondary

who exactly is checking this serial number. i guess the dns-server hosting
the secondary zone. or does the primary dns trigger this event ?

thanx alot
tim




"W C Hull" <(E-Mail Removed)> schrieb
im Newsbeitrag news:O$(E-Mail Removed)...
> Each primary and secondary zone of the same name on two separate DNS
> servers contains a serial number. Peroidically a check is made to
> determine if the serial number of the primary matches the secondary. If
> they do, nothing happens. If they don't then the secondary zone is locked
> and the secondary zone gets the changes (i.e. adds, deletes and changes)
> to the zone. Note that I said changes as this makes the update process
> quicker. This process repeats over and over again day after day.
>
> A reload from master is a manual process kicked off by executing a
> DNSCMD.EXE command line request or by requesting the process though the
> DNS Managment Console on the server performing your DNS functions. When
> such a request is made the secondary copy get a full and complete reload
> of the zone from the primary without regard to the serial numbers or the
> time. Reloads can be done whenever and however frequently you want.
>
> A reload of the Primary zone is typically performed from the Managment
> Console. When you invoke the console and display a zone the records in
> the zone are cached. When you request a reload you are asking that the
> cache be completely replaced.
>
>
> "Tim Moor" <(E-Mail Removed)> wrote in message
> news:4432edf5$(E-Mail Removed)...
>> dear dns gurus,
>> can someone please give me a short explanation about the difference from
>> a zone transfer to the reload of a zone in w2k3 dns environment.
>>
>> thank you very much
>> tim
>>
>>
>>
>
>

The secondaries all call home to mom (the primary DNS). The secondaries are
set to pull the info from one or more primary DNS. Typically the primaries
are told who they can transfer to or are set to transfer to secondary that
asks.

--


----------------------------------------------------
This mailbox protected from junk email by MailFrontier Desktop
from MailFrontier, Inc. http://info.mailfrontier.com

"Tim Moor" <(E-Mail Removed)> wrote in message
news:443386c9$(E-Mail Removed)...
> thank you very much for your information. one more question:
>
>> Peroidically a check is made to determine if the serial number of the
>> primary matches the secondary
>
> who exactly is checking this serial number. i guess the dns-server hosting
> the secondary zone. or does the primary dns trigger this event ?
>
> thanx alot
> tim
>
>
>
>
> "W C Hull" <(E-Mail Removed)> schrieb
> im Newsbeitrag news:O$(E-Mail Removed)...
>> Each primary and secondary zone of the same name on two separate DNS
>> servers contains a serial number. Peroidically a check is made to
>> determine if the serial number of the primary matches the secondary. If
>> they do, nothing happens. If they don't then the secondary zone is
>> locked and the secondary zone gets the changes (i.e. adds, deletes and
>> changes) to the zone. Note that I said changes as this makes the update
>> process quicker. This process repeats over and over again day after day.
>>
>> A reload from master is a manual process kicked off by executing a
>> DNSCMD.EXE command line request or by requesting the process though the
>> DNS Managment Console on the server performing your DNS functions. When
>> such a request is made the secondary copy get a full and complete reload
>> of the zone from the primary without regard to the serial numbers or the
>> time. Reloads can be done whenever and however frequently you want.
>>
>> A reload of the Primary zone is typically performed from the Managment
>> Console. When you invoke the console and display a zone the records in
>> the zone are cached. When you request a reload you are asking that the
>> cache be completely replaced.
>>
>>
>> "Tim Moor" <(E-Mail Removed)> wrote in message
>> news:4432edf5$(E-Mail Removed)...
>>> dear dns gurus,
>>> can someone please give me a short explanation about the difference from
>>> a zone transfer to the reload of a zone in w2k3 dns environment.
>>>
>>> thank you very much
>>> tim
>>>
>>>
>>>
>>
>>
>
>

thank you for the hint
tim


"W C Hull" <(E-Mail Removed)> schrieb
im Newsbeitrag news:%(E-Mail Removed)...
> The secondaries all call home to mom (the primary DNS). The secondaries
> are set to pull the info from one or more primary DNS. Typically the
> primaries are told who they can transfer to or are set to transfer to
> secondary that asks.
>
> --
>
>
> ----------------------------------------------------
> This mailbox protected from junk email by MailFrontier Desktop
> from MailFrontier, Inc. http://info.mailfrontier.com
>
> "Tim Moor" <(E-Mail Removed)> wrote in message
> news:443386c9$(E-Mail Removed)...
>> thank you very much for your information. one more question:
>>
>>> Peroidically a check is made to determine if the serial number of the
>>> primary matches the secondary
>>
>> who exactly is checking this serial number. i guess the dns-server
>> hosting the secondary zone. or does the primary dns trigger this event ?
>>
>> thanx alot
>> tim
>>
>>
>>
>>
>> "W C Hull" <(E-Mail Removed)>
>> schrieb im Newsbeitrag news:O$(E-Mail Removed)...
>>> Each primary and secondary zone of the same name on two separate DNS
>>> servers contains a serial number. Peroidically a check is made to
>>> determine if the serial number of the primary matches the secondary. If
>>> they do, nothing happens. If they don't then the secondary zone is
>>> locked and the secondary zone gets the changes (i.e. adds, deletes and
>>> changes) to the zone. Note that I said changes as this makes the update
>>> process quicker. This process repeats over and over again day after
>>> day.
>>>
>>> A reload from master is a manual process kicked off by executing a
>>> DNSCMD.EXE command line request or by requesting the process though the
>>> DNS Managment Console on the server performing your DNS functions. When
>>> such a request is made the secondary copy get a full and complete reload
>>> of the zone from the primary without regard to the serial numbers or the
>>> time. Reloads can be done whenever and however frequently you want.
>>>
>>> A reload of the Primary zone is typically performed from the Managment
>>> Console. When you invoke the console and display a zone the records in
>>> the zone are cached. When you request a reload you are asking that the
>>> cache be completely replaced.
>>>
>>>
>>> "Tim Moor" <(E-Mail Removed)> wrote in message
>>> news:4432edf5$(E-Mail Removed)...
>>>> dear dns gurus,
>>>> can someone please give me a short explanation about the difference
>>>> from a zone transfer to the reload of a zone in w2k3 dns environment.
>>>>
>>>> thank you very much
>>>> tim
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>