[bind10-dev] Thoughts on Architecture of Xfrin & Notify-In/Out

[ZhangLikun]

Some thinking on xfrin & notify-in/out architecture, discussed with Shane
and Feng.

 

1.  Xfrin Architecture

 

Xfrin process will maintain the zone contents according refresh/expire time
in soa record, and also zone transfer-in can be triggered by the notify-in
message. 

Xfrin process should send out notify-out message to proper slave servers
when finishing transfer-in. At the end of our discussion, we got a new name
for xfrin process: ‘ZoneRefresher’.  ‘ZoneRefresher’ will do zone
maintenance and notify its slave servers, and also provide one command
“notify-out”, by which, user can send notify message to some dns server.

 

2.  Notify In

Auth deamon should reply notify-in message.

When auth deamon receives notify message, first do ACL check, then reply the
notify message or discard it. If notify message is allowed, auth deamon
needs send the notify information (zone name, master address, port, or soa
serial?) to ZoneRefresher over cc-channel(msgq).

 

3   Zone Configuration

 

The configuration of zones, e.g., masters, allow-transfer, also-notify,
allow-notify,  will be saved in datasource, in different tables, like

 

table_zone_records

table_zone_names

table_zone_masters

table_zone_allow_transfers

table_zone_also_notify (or merge table_allow_transfer, table_also_notify to
one table)

 

There are two ways to change zone’s configuration:

=1=  (Free datasource) Run datasource as a daemon process, so user can send
configuration-change command to datasource deamon through bindctl or
webtools.

=2=  (Captive datasource) BIND10 runs with static datasource, user can
change zone configuration by through the special command (zoneconfig?)
provided by cmdctl.

Jelte, can you give some advice on configuration here?

 

 

Zhang Likun

  _____  

Zhang Likun （张立坤）

DNS Lab, CNNIC Labs

Phone: 8610-58813250

Email: zhanglikun at cnnic.cn

MSN: kerryzhang1227 at hotmail.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20100513/63c9f08a/attachment.html>