mirror of
https://github.com/StackExchange/dnscontrol.git
synced 2025-01-13 19:07:57 +08:00
9812ecd9ff
* github.com/miekg/dns * Greatly simplify the logic for handling serial numbers. Related code was all over the place. Now it is abstracted into one testable method makeSoa. This simplifies code in many other places. * Update docs/_providers/bind.md: Edit old text. Add SOA description. * SOA records are now treated like any other record internally. You still can't specify them in dnsconfig.js, but that's by design. * The URL for issue 491 was wrong in many places * BIND: Clarify GENERATE_ZONEFILE message
69 lines
2 KiB
Markdown
69 lines
2 KiB
Markdown
---
|
|
name: BIND
|
|
title: BIND Provider
|
|
layout: default
|
|
jsId: BIND
|
|
---
|
|
# BIND Provider
|
|
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.
|
|
|
|
|
|
## Configuration
|
|
The BIND provider does not require anything in `creds.json`. However
|
|
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).
|
|
|
|
{% highlight json %}
|
|
{
|
|
"bind": {
|
|
"directory": "myzones"
|
|
}
|
|
}
|
|
{% endhighlight %}
|
|
|
|
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.
|
|
|
|
{% 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 %}
|
|
|
|
## SOA Records
|
|
|
|
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:
|
|
|
|
* If there was no SOA record, one is created using the `default_soa`
|
|
settings listed above.
|
|
* When generating a new zonefile, the SOA serial number is
|
|
updated.
|
|
|
|
DNSControl ties 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 `dnscontrol push`
|
|
as normal.
|