Skip to content
Synchronize your DNS to multiple providers from a simple DSL
Go JavaScript Other
Branch: master
Clone or download

Latest commit

Latest commit e230c7a May 23, 2020

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build Update github.com/StackExchange/dnscontrol/v2 Apr 14, 2020
cmd/convertzone Update github.com/StackExchange/dnscontrol/v2 Apr 14, 2020
commands get-zones should comment out NAMESERVER() (#743) May 22, 2020
docs Document IP() is IPv4 only (#744) May 22, 2020
integrationTest CLOUDFLAREAPI: disable failing integration tests for unicode May 23, 2020
models linting (#693) Mar 10, 2020
pkg 'get-certs' permissions too open (#745) May 22, 2020
providers Update DNSimple Provider to api client 0.62 (#739) May 13, 2020
vendor GCLOUD: go get -u google.golang.org/api May 23, 2020
.gitignore ignore nupkgs Jan 9, 2020
.prettierrc Format helpers.js (#205) Sep 15, 2017
.travis.yml upgrade go version to 1.14 (#676) Mar 2, 2020
Dockerfile upgrade go version to 1.14 (#676) Mar 2, 2020
LICENSE migrate code for github Aug 23, 2016
OWNERS New provider: AXFR+DDNS (#259) (#729) May 8, 2020
README.md New provider: AXFR+DDNS (#259) (#729) May 8, 2020
azure-pipelines.yml Internals: Switch to v2 go.mod, drop GOPATH, and fix Azure Pipelines (#… Jan 28, 2020
build.ps1 Internals: Switch to v2 go.mod, drop GOPATH, and fix Azure Pipelines (#… Jan 28, 2020
dnscontrol.nuspec add chocolatey spec Jan 9, 2020
go.mod GCLOUD: go get -u google.golang.org/api May 23, 2020
go.sum GCLOUD: go get -u google.golang.org/api May 23, 2020
main.go Release v3.1.1 May 23, 2020
package-lock.json AZURE_DNS: Add support for Alias: AZURE_ALIAS() (#675) Mar 2, 2020

README.md

DNSControl

Build Status Gitter chat Google Group chat

DNSControl is a system for maintaining DNS zones. It has two parts: a domain specific language (DSL) for describing DNS zones plus software that processes the DSL and pushes the resulting zones to DNS providers such as Route53, Cloudflare, and Gandi. It can send the same DNS records to multiple providers. It even generates the most beautiful BIND zone files ever. It runs anywhere Go runs (Linux, macOS, Windows). The provider model is extensible, so more providers can be added.

Currently supported DNS providers:

  • AWS Route 53
  • Active Directory
  • AXFR+DDNS
  • Azure DNS
  • BIND
  • ClouDNS
  • Cloudflare
  • deSEC
  • DNSimple
  • DigitalOcean
  • Exoscale
  • Gandi
  • Google DNS
  • HEXONET
  • Internet.bs
  • Linode
  • NS1
  • Name.com
  • Namecheap
  • OVH
  • OctoDNS
  • OpenSRS
  • SoftLayer
  • Vultr

At Stack Overflow, we use this system to manage hundreds of domains and subdomains across multiple registrars and DNS providers.

You can think of it as a DNS compiler. The configuration files are written in a DSL that looks a lot like JavaScript. It is compiled to an intermediate representation (IR). Compiler back-ends use the IR to update your DNS zones on services such as Route53, Cloudflare, and Gandi, or systems such as BIND and Active Directory.

An Example

dnsconfig.js:

// define our registrar and providers
var namecom = NewRegistrar("name.com", "NAMEDOTCOM");
var r53 = NewDnsProvider("r53", "ROUTE53")

D("example.com", namecom, DnsProvider(r53),
  A("@", "1.2.3.4"),
  CNAME("www","@"),
  MX("@",5,"mail.myserver.com."),
  A("test", "5.6.7.8")
)

Running dnscontrol preview will talk to the providers (here name.com as registrar and route 53 as the dns host), and determine what changes need to be made.

Running dnscontrol push will make those changes with the provider and my dns records will be correctly updated.

See Getting Started page on documentation site.

Benefits

  • Less error-prone than editing a BIND zone file.
  • More reproducible than clicking buttons on a web portal.
  • Easily switch between DNS providers: The DNSControl language is vendor-agnostic. If you use it to maintain your DNS zone records, you can switch between DNS providers easily. In fact, DNSControl will upload your DNS records to multiple providers, which means you can test one while switching to another. We've switched providers 3 times in three years and we've never lost a DNS record.
  • Adopt CI/CD principles to DNS! At StackOverflow we maintain our DNSControl configurations in Git and use our CI system to roll out changes. Keeping DNS information in a VCS means we have full history. Using CI enables us to include unit-tests and system-tests. Remember when you forgot to include a "." at the end of an MX record? We haven't had that problem since we included a test to make sure Tom doesn't make that mistake... again.
  • Adopt PR-based updates. Allow developers to send updates as PRs, which you can review before you approve.
  • Variables save time! Assign an IP address to a constant and use the variable name throughout the file. Need to change the IP address globally? Just change the variable and "recompile."
  • Macros! Define your SPF records, MX records, or other repeated data once and re-use them for all domains.
  • Control Cloudflare from a single source of truth. Enable/disable Cloudflare proxying (the "orange cloud" button) directly from your DNSControl files.
  • Keep similar domains in sync with transforms and other features. If one domain is supposed to be a filtered version of another, this is easy to set up.
  • It is extendable! All the DNS providers are written as plugins. Writing new plugins is very easy.

Installation

From source

DNSControl can be built with Go version 1.14 or higher. To install, simply run

go get github.com/StackExchange/dnscontrol

dnscontrol will be installed in $GOPATH/bin

Via packages

Get prebuilt binaries from github releases

Alternatively, on Mac you can install it using homebrew:

brew install dnscontrol

Via docker

docker run --rm -it -v $(pwd)/dnsconfig.js:/dns/dnsconfig.js -v $(pwd)/creds.json:/dns/creds.json stackexchange/dnscontrol dnscontrol preview

More info at our web site

https://stackexchange.github.io/dnscontrol/

You can’t perform that action at this time.