Slave zone transfer issues

Spain, Dr. Jeffry A. spainj at countryday.net
Thu Dec 8 00:38:15 UTC 2011


>> To test the zone updating process, I used nsupdate on the master to add the record "bind10.jaspain.net. AAAA 2001:4870:20ca:158:14ff:7695:9632:e9ec". Although "also-notify { 2001:4870:20ca:158:14ff:7695:9632:e9ec; };" is configured for the jaspain.net zone, there is no indication that a zone transfer to the bind10 slave occurred after the update. A bind9.9.0b2 slave was updated properly. Is there something that I need to configure on bind10 to allow it to process notify messages?

>Hmm, assuming you still have this in your configuration:
>"Xfrin": {"zones": [{"name": "jaspain.net", "master_addr": "2001:4870:20ca:158:4423:f19d:4ead:5c20"}]}

It now reads as follows:
{"Xfrin": {"zones": [{"name": "jaspain.net", "master_addr": "2001:4870:20ca:158:4423:f19d:4ead:5c20"}]}, "version": 2, "Zonemgr": {"secondary_zones": [{"name": "jaspain.net", "class": "IN"}]}}

> and your BIND 9 master server really sent the notify from 2001:4870:20ca:158:4423:f19d:4ead:5c20 (maybe you want to check if the master server has multiple IPv6 addresses and might use a different one to send the notify), I believe it should immediately trigger a retransfer.  Perhaps you have a log starting with XFRIN_NOTIFY_UNKNOWN_MASTER?

I will set up logging on bind10 and attempt to reproduce this. For the record, according to the master's log, bind10 did request an AXFR from the master almost exactly four hours after the master indicated that it sent out the notify message. That AXFR was successful. Thanks. Jeff.



More information about the bind10-users mailing list