dnscontrol/docs/_providers/bind.md

47 lines
1.2 KiB
Markdown
Raw Normal View History

2017-01-12 04:02:45 +08:00
---
name: BIND
title: BIND Provider
2017-01-12 04:02:45 +08:00
layout: default
jsId: BIND
---
# BIND Provider
2017-01-12 04:02:45 +08:00
2017-08-30 01:49:39 +08:00
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.