bind2nsd 

 

BIND-to-NSD "zone" Translation

In the table that follows, we document what BIND construct in the zone clause gets translated to which NSD construct. If there is no entry in the "NSD equivalent" column, no translation has been implemented yet.

The opening of the BIND zone clause becomes: 

   zone:
      name: "<name-as-provided>"

zone statement NSD3 equivalent Notes
allow-notify { <ip-addr-list> };

For master zones, an include for an empty ACL file, plus a notify: for each address in the list: 

	    include: "<acl-file>"
	    notify: <ip-addr> NOKEY

For slave zones, one pair for each address in the list: 

	    allow-notify: <ip-addr> NOKEY
	    request-xfr: <ip-addr> NOKEY

For masters, all addresses listed in the also-notify statement of the options clause will also be named in a notify statement.

For slaves, all addresses listed in the allow-notify statement of the options clause will also be named in an allow-notify statement.

allow-query { <ip-addr-list> }; none currently recognized but ignored; NSD has no equivalent
allow-recursion { <ip-addr-list> }; none recognized but ignored; NSD does not do recursion
allow-transfer { <ip-addr-list> };

For each IP address, issue two lines in the zone: section: 

	    provide-xfr: <ip-addr> NOKEY
	    notify: <ip-addr> NOKEY

If the IP address has been mentioned in a server clause and is associated with a key, the NOKEY string will be replaced with the key name. If this statement is used in the zone clause, it overrides any settings in the options clause.
allow-update-forwarding { <ip-addr-list> };    
also-notify { <ip-addr-list> };

For master zones only, one notify for each address in the list: 

	    notify: <ip-addr> NOKEY

For masters, all addresses listed in the also-notify statement of the options clause will also be named in a notify statement.
alt-transfer-source { <ip-addr-list> };    
alt-transfer-source-v6 { <ip-addr-list> };    
check-names (warn | fail | ignore);    
database "<filename>";    
delegation-only { <ip-addr-list> };    
dialup (no | yes | notify | refresh | passive | notify-passive);   is this still in active use?
file "<filename>"; zonefile: "<filename>"  
forward { <ip-addr-list> };    
forwarders { <ip-addr-list> };    
ixfr-from-differences { <ip-addr-list> };    
key-directory "<dirname>";    
max-journal-size <number>;    
max-refresh-time <number>;    
max-retry-time <number>;    
max-transfer-idle-in <number>;    
max-transfer-idle-out <number>;    
max-transfer-time-in <number>;    
max-transfer-time-out <number>;    
min-refresh-time <number>;    
min-retry-time <number>;    
multi-master { <ip-addr-list> };    
notify { <ip-addr-list> };    
notify-source { <ip-addr-list> };    
notify-source-v6 { <ip-addr-list> };    
sig-validity-interval <number>;    
transfer-source { <ip-addr-list> };    
transfer-source-v6 { <ip-addr-list> };    
type (master | slave | forward | hint | stub | delegation-only); no direct translation Interacts with allow-notify and also-notify statements differently for master and slave.
update-policy ( | );    
use-alt-transfer-source { <ip-addr-list> };    
Support This Project Last updated: 24 July 2007 SourceForge.net Logo