bind2nsd

BIND-to-NSD "options" Translation

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

The statements in the BIND options clause become parts of the NSD3 server: clause.

NB: there are an incredible number of options, and not nearly enough are being handled just yet.

`options` statement	NSD3 equivalent	Notes
`additional-from-auth`
`additional-from-cache`
`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> 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 each master zone. For slaves, all addresses listed in the `allow-notify` statement of the `options` clause will also be named in an `allow-notify` statement for each slave zone.
`allow-query { <ip-addr-list> };`	none	currently recognized but ignored; there is no NSD equivalent
`allow-recursion { <ip-addr-list> };`	none	currently recognized but ignored; NSD does not do recursion
`allow-transfer { <ip-addr-list> };`	`provide-xfr: <ip-address> NOKEY` `notify: <ip-address> NOKEY`	Create the pair of statements for each IP address in the list, for each zone defined, unless there's an `allow-transfer` in a `zone` clause which overrides the global one in the `options` clause. If a `server` clause has associated the IP address with a key, the key name will be written instead of the `NOKEY` string.
`allow-update-forwarding`
`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`
`alt-transfer-source-v6`
`auth-nxdomain`
`avoid-v4-udp-ports`
`avoid-v6-udp-ports`
`blackhole`	none	NSD has no real equivalent; a warning will be given when this statement is encountered because responses will be given to queries that should go in the blackhole.
`check-names (master \| slave \| response) (fail \| warn \| ignore)`		currently recognized but ignored
`cleaning-interval`		currently recognized but ignored (in options only)
`coresize`	none	currently recognized but ignored
`datasize`		currently being ignored
`dialup`
`directory "<dirname>";`	`zonesdir: <dirname>`	While this could be translated as `zonesdir`, the path to each zonefile is rewritten so that it can be placed in a single directory tree along with all other translated files. The reasoning is that this should allow the translation to take place in complete isolation, without tampering with anything else the system may be doing.
`disable-algorithm`
`dnssec-enable`
`dnssec-lookaside`
`dnssec-must-be-secure`
`dual-stack-servers`
`dump-file`	none	currently recognized but ignored
`edns-udp-size`
`files`
`forward`
`forwarders`
`heartbeat-interval`
`hostname`
`interface-interval`		currently being ignored
`ixfr-from-differences`
`key-directory`
`lame-ttl`
`listen-on`
`listen-on-v6`
`match-mapped-addresses`
`max-cache-size`		currently being ignored
`max-cache-ttl`
`max-ncache-ttl`
`max-journal-size`
`max-refresh-time`
`max-retry-time`
`max-transfer-idle-in`
`max-transfer-idle-out`
`max-transfer-time-in`
`max-transfer-time-out`
`memstatistics-file`
`min-refresh-time`
`min-retry-time`
`minimal-responses`
`multi-master`
`notify`
`notify-source`
`notify-source-v6`
`pid-file "<filename>";`	`pidfile: <filename>`	direct translation
`port`
`preferred-glue`
`provide-ixfr`
`query-source`
`query-source-v6`
`querylog`
`recursing-file`
`random-device`
`recursion`
`recursive-clients <number>;`		currently recognized but ignored
`request-ixfr`
`root-delegation-only`
`rrset-order`
`serial-queries`
`serial-query-rate`
`server-id`
`sortlist`
`stacksize`		currently being ignored
`statistics-file "<filename>";`	none	Currently, there's not a good way to translate this; NSD3 wants an integer flag (for the `statistics:` statement), but BIND is telling the DNS where to store data. Hence, this is recognized for now, but ignored.
`sig-validity-interval`
`tcp-clients`
`tcp-listen-queue`
`tkey-dhkey`
`tkey-domain`
`tkey-gssapi-credential`
`transfer-format (one-answer \| many-answers);`	none	currently recognized but ignored
`transfer-source`
`transfer-source-v6`
`transfers-in`
`transfers-out`
`transfers-per-ns`
`use-alt-transfer-source`
`use-ixfr`
`version`	none	currently recognized but ignored
`zone-statistics`

Last updated: 24 July 2007