This provider maintains a directory with a collection of .zone files.
This provider does not generate or update the named.conf file, nor does it deploy the .zone files to the BIND master. Both of those tasks are different at each site, so they are best done by a locally-written script.
The BIND provider does not require anything in
you can specify a
directory where the provider will look for and create zone files. The default is the
zones directory (in the current directory).
The BIND accepts some optional metadata via your DNS config when you create the provider:
In this example we set the default SOA settings and NS records.
filenameformat parameter specifies the file name to be used when
writing the zone file. The default is acceptable in most cases: the
name as specified in the
D() function, plus “.zone”.
The filenameformat is a string with a few printf-like
%Uthe domain name as specified in
%Dthe domain name without any split horizon tag
%Tthe split horizon tag, or “”, see
xif the split horizon tag is non-null, otherwise nothing.
xcan be any printable.
%) are copied unchanged to the output stream
/or other filesystem separators result in undefined behavior
%T%*U%D.zone(optional tag and
_+ domain +
The last example will generate the same name for both
assumes two BIND providers are configured in
creds.json, eacch with
directory setting. Otherwise
dnscontrol will write
both domains to the same file, flapping between the two back and
get-zones all subcommand scans the directory for
any files named
*.zone and assumes they are zone files.
dnscontrol get-zones --format=nameonly - BIND all
filenameformat is defined,
dnscontrol makes an guess at which
filenames are zones but doesn’t try to hard to get it right, which is
mathematically impossible in all cases. Feel free to file an issue if
your format string doesn’t work. I love a challenge!
DNSControl assumes that SOA records are managed by the provider. Most providers simply generate the SOA record for you and do not permit you to control it at all. The BIND provider is unique in that it must emulate what most DNS-as-a-service providers do.
When DNSControl reads a BIND zonefile:
default_soasettings listed above.
DNSControl tries to maintain the serial number as yyyymmddvv. If the existing serial number is significantly higher it will simply increment the value by 1.
If you need to edit the SOA fields, the best way is to edit the
zonefile directly, then run
dnscontrol preview and