1d9d2b1a19
* starting to refactor commands * work * not sure * all commands working! * actually add file * work in delay flag again * start to refactor out console printing * i hate line endings * simple travis test to find direct output * remove all direct printing from push/preview * checkin vendor * don't need this yet * forgot to commit these * make version explicit command * some code review * Add "check" subcommand. * move stuff to commands package * fix * comment out check for printlns. for now * alphabet hax * activedir flags gone. use creds instead * active dir doc update * remove bind specific flags. creds instead * default to zones dir * fix linux build * fix test * cleanup random global* vars * Clean up PowerShell docs * rename dump-ir to print-ir. combine with print-js
1.2 KiB
| name | layout | jsId |
|---|---|---|
| Bind | 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.mydomain.com.', 'mbox': 'sysadmin.mydomain.com.', 'refresh': 3600, 'retry': 600, 'expire': 604800, 'minttl': 1440, }, 'default_ns': [ 'ns1.mydomain.com.', 'ns2.mydomain.com.', 'ns3.mydomain.com.', 'ns4.mydomain.com.' ] }) {% endhighlight %}
If you need to customize your SOA or NS records, you can do it with this setup.