mirror/stackexchange-dnscontrol
1
0
Fork 0
mirror of https://github.com/StackExchange/dnscontrol.git synced 2024-05-11 05:55:12 +00:00
Code Issues Releases Activity

NEW PROVIDER: OctoDNS (#309)

Browse Source 
* govendor gopkg.in/yaml.v2
* Ignore YAML and BIND test data litter.  Create README.txt files to force git to create subdirectories.
* Update convertzone to also read OctoDNS files
This commit is contained in:
Tom Limoncelli
2018-02-27 17:36:47 -05:00
committed by GitHub
parent b83630044f
commit 54de1ff698
58 changed files with 11708 additions and 118 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/getting-started.md
View File

@@ -31,7 +31,8 @@ like [git-crypt](https://www.agwa.name/projects/git-crypt) or
Create a subdirectory called `zones` in the same directory as the
configuration files. (`mkdir zones`). `zones` is where the BIND
provider writes the zonefiles it creates.
provider writes the zonefiles it creates. Even if you don't
use BIND, it is useful for testing.
## 3. Create the initial `dnsconfig.js`
@@ -246,7 +247,7 @@ You can manually create the `D()` statements, or you can
generate them automatically using the
[convertzone](https://github.com/StackExchange/dnscontrol/blob/master/cmd/convertzone/README.md)
utility that is included in the DNSControl repo (it converts
BIND-style zone files to DNSControl's language).
BIND-style zone files and OctoDNS-style YAML files to DNSControl's language).
Now you can make change to the domain(s) and run `dnscontrol preview`
@@ -258,4 +259,4 @@ If you are going to use this in production, we highly recommend the following:
* Store the configuration files in Git.
* Encrypt the `creds.json` file before storing it in Git.
* Use a CI/CD tool like Jenkins to automatically push DNS changes.
* Join the DNSControl community. File [issues and PRs](https://github.com/StackExchange/dnscontrol).
* Join the DNSControl community. File [issues and PRs](https://github.com/StackExchange/dnscontrol).