2017-01-11 13:02:45 -07:00
---
2017-10-11 08:33:17 -04:00
name: BIND
title: BIND Provider
2017-01-11 13:02:45 -07:00
layout: default
jsId: BIND
---
2017-10-11 08:33:17 -04:00
# BIND Provider
2017-10-11 11:59:29 -04:00
This provider maintains a directory with a collection of .zone files.
2017-03-22 10:38:08 -06:00
## Configuration
2017-09-13 10:00:41 -04:00
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.
2017-10-11 11:59:29 -04:00
{% highlight json %}
2017-09-13 10:00:41 -04:00
{
2017-10-11 08:33:52 -04:00
"bind": {
2017-09-13 10:00:41 -04:00
"directory": "myzones"
}
}
{% endhighlight %}
2017-10-11 11:59:29 -04:00
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:
2017-03-22 10:38:08 -06:00
{% highlight javascript %}
2017-10-11 08:33:52 -04:00
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.'
]
2017-03-22 10:38:08 -06:00
})
{% endhighlight %}
2017-10-11 11:59:29 -04:00
If you need to customize your SOA or NS records, you can do so with this setup.