notify
Hu, Xiaodong
XHu at imps0014.us.dg.com
Wed Nov 1 22:53:42 UTC 2000
I am new on this, I am trying to give my view:
suppose you have zone us.hosts, you add notify yes; in slave you have zone
us.hosts.bak;
the master ( master IP;); I also put notify yes; if you use poll algo., you
notify us.hosts
and increment serial #, then you use kill to -HUP to load us.hosts and do
same thing in
slave machine, then slave's us.hosts.bak synchronize with us.hosts; now you
use notify
option in slave machine you don't need to kill -HUP, slave get notify then
it compare
its serial # with us.hosts in master machine, if its # lower than master's,
it do zone
transfer; I did this trial in lab. there is a trick there, we need to
explicitly put slave
machine in us.hosts, ( IN NS slave's IP), the book just mentioned
change in
named.conf, doesn't mention change in db file.
Xiaodong Hu
-----Original Message-----
From: Andreas Gietl [mailto:gietl at gietl.com]
Sent: Wednesday, November 01, 2000 3:55 PM
To: comp-protocols-dns-bind at moderators.isc.org
Subject: notify
what would cause a primary bind-ns to send notifies to his slaves for
all zones that changed?
thx
andreas
--
andreas gietl
gietl internet services
fon +49 9402 2551
fax +49 9402 2604
mobile +49 171 60 70 008
gietl at gietl.com
############################################
# Das Handbuch sagt, das Programm benotige #
# Windows 95 oder besser. Also habe ich #
# Linux installiert! #
############################################
More information about the bind-users
mailing list