[bind10-dev] zonemgr / notify out questions

[Jeremy C. Reed]

(I will respond to the previous replies later ...)


13) When adding new zones to the sqlite3 database (via b10-loadzone) or 
reloading same zones, b10-zonemgr doesn't recognize them.


14) What is expected way to configure this? Load a zone into the sqlite3 
database? (That is what I do now.) What is planned for flagging a zone 
as a secondary or primary? What about some command/configuration to name 
the zone(s) and their masters?


15) zonemgr triggered a AXFR even though SOA serial was not increased.
tcpdump shows me that the SOA query and response does happen before the 
AXFR. (My master and the local BIND 10 have identical zone file loaded 
-- no serial change.)

[b10-zonemgr] Do refresh for zone (foo., IN).
[b10-xfrin] transfer of 'foo.': AXFR started
[b10-xfrin] transfer of 'foo.': AXFR succeeded


16) Xfrout logged that it received a notify command. While it does say 
"command" this may be confusing and unclear:

09-Sep-2010 13:06:39.104 Xfrout: INFO: Receive notify command for 
zone:'foo./IN'

This may make an admin think that Xfrout received a DNS NOTIFY message.

I suggest using something more precise and unique, like "notify_others 
command". (This also is similar to my #6 comment in previous email.)


17)  zonemgr expired a zone where the serial was not increased. This may 
be same problem as above #15.

[b10-zonemgr] Zone (foo., IN) is expired.


18) Expired zones are still served. I can not find any RFC that says the 
data should stop being served though. Please, can anyone let me know 
what RFC or document defines the correct behavior? (I also asked about 
this on internal ISC list.)