BIND-to-NSD Configuration Translation

This project builds scripts that translate DNS information in BIND format to NSD format, and then copy that translation to an NSD server. The goal is to make it simple to run redundant BIND and NSD servers and keep them in sync, using only the BIND configuration files.

In the tables that follow, we document what BIND construct gets translated to which NSD construct.

Translation Tables

Please note that these are not currently complete. That is to say, not all BIND constructs are translated, and it is possible that we've missed a few completely. Corrections and additions are always welcome.

BIND configuration clauses and their corresponding translations:

• acl -- these clauses will be recognized, and all uses of any given acl replaced with the defined IP address match list when they are encountered.
• controls -- parsed and ignored, not implemented in NSD3
• include -- while this is not strictly a clause, files are included inline and translated as they are encountered.
• key -- this clause is parsed, but only partially translated. Completing this is on the TODO list for 0.5.x.
• logging -- parsed and ignored, not implemented in NSD3
• lwres -- parsed and ignored, not implemented in NSD3
• masters -- TBD
• options -- conversion table
• server -- conversion table
• trusted-keys -- parsed and ignored, not implemented in NSD3
• view -- parsed and ignored, not implemented in NSD3
• zone -- conversion table

BIND-Specific DNS Directives

One can include certain directives in the zone files. NSD handles the standardized ones. The $GENERATE directive, however, is not yet standardized but still commonly used.

The bind2nsd scripts will look for $GENERATE in the zone files and expand it as appropriate. The version of $GENERATE currently handled is of this form:

   $GENERATE <start>-<stop> [ <step> ] <left-hand-side> <type> <right-hand-side>

<start>

the beginning value (a number) for the generated sequence

<stop>

the final value (a number) for the generated sequence

<step>

an optional value (a number) added on each iteration (default: 1)

<left-hand-side>

the text pattern to be used before the <type> string. The string '$' will be replaced with the current value of the iteration.

<type>

one of the strings CNAME, NS, A, AAAA, DNAME, or PTR

<right-hand-side>

the text pattern to be used after the <type> string. The string '$' will be replaced with the current value of the iteration.

Caveat Emptor

There is little rigorous checking done of the BIND information (some must obviously be done, but it is not exhaustive). Remember: the named-checkconf command is your friend.

Last updated: 17 July 2007