Slave zone transfer issues

JINMEI Tatuya / 神明達哉 jinmei at isc.org
Wed Dec 7 05:13:17 UTC 2011


At Wed, 7 Dec 2011 04:29:32 +0000,
"Spain, Dr. Jeffry A." <spainj at countryday.net> wrote:

> This resulted in the following line in /var/bind10-devel/b10-config.db:
> {"Xfrin": {"zones": [{"name": "jaspain.net", "master_addr": "2001:4870:20ca:158:4423:f19d:4ead:5c20"}]}, "version": 2}
> 
> Following this "dig @localhost jaspain.net soa" returned status REFUSED. The master, which is running bind9.9.0b2, showed no zone transfer activity in its syslog.
> 
> Should the configuration of a secondary zone in bind10 automatically trigger a request to transfer the zone, or must it be transferred manually the first time, or did I do something wrong?

It won't be automatically triggered just by adding a "zones"
configuration to Xfrin.  You'll also have to register the zone in the
"Zonemgr" configuration:

config add Zonemgr/secondary_zones
config set Zonemgr/secondary_zones[0]/name "jaspain.net"
config commit

But even doing this wouldn't immediately trigger the zone transfer.
So, in practice, for the first time it's probably better to trigger it
by hand via the "retransfer" command as you actually did (you'll still
need the Zonemgr configuration to keep track of further changes to the
zone).

We know it's not convenient - configuration information about zones
should be centralized.  That will be improved in future versions.
(I also noticed the BIND 10 guide is not very helpful; it doesn't show
a configuration example of Zonemgr or explain it's crucial for a
secondary server to make zone transfers.  This should also be improved).

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.



More information about the bind10-users mailing list