A server-side entry in TopGit's GitHub warehouse: StackExchange/dnscontrol, 4.0k stars, Backend, Go. Infrastructure as code for DNS!
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
DNSControl is Infrastructure as Code for DNS.
It includes a full-featured configuration language (Javascript-compatible),
plus "plug-ins" that speak to DNS provider APIs such as AWS Route 53,
Cloudflare, and Gandi. It can send the same DNS records to multiple providers.
It runs anywhere Go runs (Linux, macOS, Windows). The provider model is
extensible, so more providers can be added.
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.
The easiest way to run DNSControl is to use the Docker container:
docker run --rm -it -v "$(pwd):/dns" ghcr.io/dnscontrol/dnscontrol preview
Getting Started
The quickest way to start is dnscontrol init. The interactive wizard asks for your DNS provider and registrar, verifies your credentials and writes a working creds.json and dnsconfig.js, including the records that already exist in your zones.
See the Getting Started page on the documentation site for the full walkthrough.
Want full "GitOps" control of your DNS data? Clone the dns-config starter repo to get started!
Supported Providers
DNSControl supports 78 DNS providers and registrars:
AdGuard Home
Akamai Edge DNS
Alibaba Cloud DNS
Amazon Route 53¹
AutoDNS¹
AXFR + DDNS
Azure DNS
Azure Private DNS
Bunny DNS
CentralNic Reseller¹
Cloudflare
ClouDNS¹
CloudPress
Constellix
CSC Global¹
deSEC
DigitalOcean
DNS Made Easy
DNS over HTTPS²
dnscale
DNSimple¹
Domainnameshop
Dynadot²
Dynu
easyname²
Exoscale
FortiGate
G-Core Labs
Gandi v5¹
Gidinet¹
Gigahost
Google Cloud DNS
Hetzner DNS
hosting.de¹
Huawei Cloud DNS
Hurricane Electric DNS
Infoblox
Infomaniak
Internet.bs²
INWX¹
IONOS
ISC BIND
Joker.com
Linode
Loopia¹
LuaDNS
MikroTik RouterOS
Misaka.io
mittwald mStudio
Mythic Beasts
Name.com¹
Namecheap¹
Netbird
netcup
Netlify
Netnod
NexDNS
NS1
Openprovider
OpenSRS²
OpenWrt
Oracle Cloud Infrastructure
OVHcloud¹
Packetframe
Porkbun¹
PowerDNS
Realtime Register¹
RWTH Aachen
Sakura Cloud
Scaleway
SoftLayer
Spaceship¹
Tencent Cloud DNS¹
TransIP
UniFi
Vercel
Vultr
WebSupport
¹also supports registrar functions
²registrar only
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.
Apply CI/CD principles to DNS! StackOverflow maintains their
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 (GitOps) 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
DNSControl can be installed via packages for macOS, Linux and Windows, or from source code. See the official instructions.
Via GitHub Actions (GHA)
The official GitHub Action is: github.com/dnscontrol/dnscontrol-action
Others have been created such as:
github.com/metabrainz/dnscontrol-action
github.com/gacts/install-dnscontrol
Deprecation warnings (updated 2026-08-17)
REV() will switch from RFC2317 to RFC4183 sometime after v5.0 is released. This is a breaking change. Warnings are output if your configuration is affected. See https://docs.dnscontrol.org/language-reference/top-level-functions/revcompat
NAMEDOTCOM, OPENSRS, and SOFTLAYER need maintainers! These providers have no maintainer. Maintainers respond to PRs and fix bugs in a timely manner, and try to stay on top of protocol changes. Interested in being a hero and adopting them? Contact tal at what exit dot org.
Contributing
Want to contribute? Whether it's fixing a bug, adding a new DNS provider, or improving documentation, contributions are welcome. See CONTRIBUTING.md for how to get started.
More info at our website
The website: https://docs.dnscontrol.org/
The getting started guide: https://docs.dnscontrol.org/getting-started/getting-started
How does StackExchange/dnscontrol compare to other Backend projects?
StackExchange/dnscontrol is tracked by TopGit in the Backend category, with 4.0k GitHub stars and written in Go. Browse the Backend topic page on TopGit to compare it against similar projects by stars and activity.
Is StackExchange/dnscontrol open source?
Yes — StackExchange/dnscontrol ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/StackExchange/dnscontrol.
What else is in the Backend space?
StackExchange/dnscontrol is tracked by TopGit under the Backend category, alongside 4 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What is StackExchange/dnscontrol?
StackExchange/dnscontrol (StackExchange/dnscontrol) is a Go project on GitHub. From the project's own README: Infrastructure as code for DNS!
Where do I read more about StackExchange/dnscontrol?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/StackExchange/dnscontrol is the definitive source.
Why is StackExchange/dnscontrol categorized under Backend?
TopGit places StackExchange/dnscontrol in the Backend category based on its GitHub topics and description (tagged: "dns", "dnscontrol", "go"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Curious whether dnscontrol is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about dnscontrol.