55e7710b06
This appears to be the only one. Manual audit with (zsh):
pcregrep -o1 '}}/([^\)]+)\)' **/*(.)
yielded all the site-based URLs and I eye-compared them to the names of
existing docs.
2 KiB
| layout |
|---|
| default |
Getting Started
1. Get the binaries
You can either download the latest github release, or build from the go source:
go get github.com/StackExchange/dnscontrol
2. Create files
The first file you will need is a javascript file to describe your domains.
Individual providers will vary slightly. See the provider docs for specifics.
For this example we will use a single "BIND" provider that will generate zone files on our local file system.
The default name is dnsconfig.js:
{% highlight js %} var registrar = NewRegistrar("none","NONE"); // no registrar var bind = NewDnsProvider("bind","BIND");
D("example.com", registrar, DnsProvider(bind), A("@", "1.2.3.4") ); {%endhighlight%}
You may modify this file to match your particular providers and domains. See the javascript docs and the provider docs for more details. If you are using other providers, you will likely need to make a creds.json file with api tokens and other account information.
3. Run dnscontrol preview
This will print out a list of "corrections" that need to be performed. It will not actually make any changes.
4. Run dnscontrol push
This will actually generate zones/example.com.zone for you. The bind provider is more configurable, and you can read more information here.
Migrate more zones
Once you have the system working for a test zone, migrate other
zones. You can manually create the D() statements, or you can
generate them automatically using the
convertzone
utility that is included in the DNSControl repo (it converts
BIND-style zone files to DNSControl's language). To make sure the
migration is correct, use dnscontrol preview and make sure it
sees no differences.
Migrating doc gives more detailed advice.