zone transfer from slave
SW...@wiley.com
thank you very much for replying.
Is it right that the following syntax are set in config file?
min-refresh-time, max-refresh-time, min-retry-time, max-retry-time
and I guess there is no way a slave server can initiate a specific zone=
transfer on demand right?
I had used the dig axfr, though the info I pulled seemed to be in a
different format compare to when it was pull naturally.
I had been restarting the entire name server to initiate the pull, but =
I
like to know if there are other ways I don't need to restart the whole
thing.
thanks
=
=20
phn@icke-reklam.i =
=20
psec.nu To: comp-protocols=
-dns-...@isc.org =20
Sent by: cc: =
=20
bind-users-bounce Subject: Re: zone trans=
fer from slave =20
@isc.org =
=20
=
=20
=
=20
08/27/2003 11:29 =
=20
AM =
=20
=
=20
=
=20
SW...@wiley.com wrote:
> Hi all,
> We have just upgraded our BIND to 9.2.2, on Solaris 8, this server is=
> primary for some domains and secondary for others.
> I understand that slave servers can pull the zone via different means=
,
such
> as depending on the expire interval, serial number, etc. as well as
> removing the zone file on slave server.
> I have a few zone files that is located in a different location and I=
do
> not have access to. How can I pull individual zone from slave withou=
t
> restarting the entire slave name server? rndc is only executed on
primary
> server, is this correct?
> thanks very much
Slaves will poll the master at "refresh-time" and pull the zone if "ser=
ial"
is
higher at the master.
A received NOTIFY will initiate a poll.
Some tuneabals are available in bind-9 :
min-refresh-time, max-refresh-time, min-retry-time, max-retry-time
These options control the server's behavior on refreshing a zone
(querying for SOA changes) or
retrying failed transfers. Usually the SOA values for the zone are
used, but these values are set by
the master, giving slave server administrators little control over
their contents.
These options allow the administrator to set a minimum and maximum
refresh and retry time
either per-zone, per-view or globally. These options are valid for
slave and stub zones, and clamp
the SOA refresh and retry times to the specified values.
See "
http://www.ipsec.nu/dns/bind9/Bv9ARM.ch06.html#types_of_resource_record=
s_and_when_to_use_them
"
( which is a copy of "The ARM book" supplied with any distribution of
bind-9)
--
Peter H=E5kanson
IPSec Sverige ( At Gothenburg Riverside )
Sorry about my e-mail address, but i'm trying to keep spam o=
ut,
remove "icke-reklam" if you feel for mailing me. Thanx.=
=
Barry Margolin
>thank you very much for replying.
>
>Is it right that the following syntax are set in config file?
>min-refresh-time, max-refresh-time, min-retry-time, max-retry-time
If you have a good reason to override the domain administrator's SOA
settings, you could set them. They're not normally needed, though.
>and I guess there is no way a slave server can initiate a specific zone=
>transfer on demand right?
"rndc reload <zone-name>" should force the slave to initiate a refresh of
the specified zone immediately (this works in BIND 8 with "ndc", and I'm
extrapolating that it also works similarly in BIND 9 with "rndc".
>I had used the dig axfr, though the info I pulled seemed to be in a
>different format compare to when it was pull naturally.
It's not the exact same layout as BIND's built-in zone transfer, but it's
compatible, so you can use that as the zone file.
--
Barry Margolin, barry.m...@level3.com
Level(3), Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.