Slave zone transfer issues

[Spain, Dr. Jeffry A.]

I configured a slave zone on my bind10 authoritative server using bindctl as follows:

config add Xfrin/zones
config set Xfrin/zones[0]/name "jaspain.net"
config set Xfrin/zones[0]/master_addr "2001:4870:20ca:158:4423:f19d:4ead:5c20"
config commit

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?

After this I did try the bindctl command "Xfrin retransfer zone_name="jaspain.net" master=2001:4870:20ca:158:4423:f19d:4ead:5c20". This time the master did log a successful zone transfer, and "dig @localhost jaspain.net soa" returned the expected answer. "dig @localhost jaspain.net soa +dnssec" also worked as expected, returning the various RRSIG records.

I do appreciate all of you helping me work through bind10 over the past several days.

Jeffry A. Spain
Network Administrator
Cincinnati Country Day School


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind10-users/attachments/20111207/809da827/attachment.html>