31bdb65720
- Fixed indentation - Use same naming scheme for all examples (i.e. all caps for provider, REG prefix for registrar) - Use REG_NONE as registrar when provider does not provide it - Use example.tld for example domain - Use 1.2.3.1/24 IP range for examples - A few spelling fixes
1.2 KiB
| name | title | layout | jsId |
|---|---|---|---|
| BIND | BIND Provider | default | BIND |
BIND Provider
This provider simply maintains a directory with a collection of .zone files. We currently copy zone files to our production servers and restart bind via a script external to DNSControl.
Configuration
In your credentials file (creds.json), you can specify a directory where the provider will look for and create zone files. The default is the zones directory where dnscontrol is run.
{% highlight javascript %} { "bind": { "directory": "myzones" } } {% endhighlight %}
The BIND provider does not require anything in creds.json. It does accept some (optional) metadata via your dns config when you create the provider:
{% highlight javascript %} var BIND = NewDnsProvider('bind', 'BIND', { 'default_soa': { 'master': 'ns1.example.tld.', 'mbox': 'sysadmin.example.tld.', 'refresh': 3600, 'retry': 600, 'expire': 604800, 'minttl': 1440, }, 'default_ns': [ 'ns1.example.tld.', 'ns2.example.tld.', 'ns3.example.tld.', 'ns4.example.tld.' ] }) {% endhighlight %}
If you need to customize your SOA or NS records, you can do it with this setup.