before
One record, on one domain. The other hundred and eighty-six are still waiting.
The DNS relay we all wish we had.
The zone is a file you own, and it changes with one command from the terminal. dnsthing relays it to the nameservers, so a rename across two hundred records is an edit and an apply — not an afternoon of two-factor codes and confirmation emails.
Get in touch No provider chosen yet. The page is the design.
after
$ dns plan
22 zones · 187 records
+ A box.dnsthing.com 198.51.100.9
~ A www.hostingthing.com 198.51.100.7 → 198.51.100.9
$ dns apply
hostingthing.com 12 records 210 ms
rytter.it 4 records 88 ms
0xrytter.com 3 records 64 ms
…
22 zones · 187 records · 1.9 sEvery zone, applied from the same files, in the time it takes to read this.
One command for a hundred names
A zone is a file and a CLI, so a bulk change is a loop you already know how to write — and the result is checkable.
# move every www to the new box, in one pass
$ dns set 'www.*' A 198.51.100.9
matched 9 records across 9 zones
applied in 640 ms
# see what is live, without opening anything
$ dns get www.hostingthing.com
A 198.51.100.9 ttl 300 applied 2s agoRelay it your way
One stable address sits behind every name, and only that address has to stay put. Where the records are written down does not change when the relay behind them does.
- Over dnsthing
- Two NS records at the registrar, once per domain. dnsthing answers from there on, and every change is an apply from the same files as the rest. zones/ → dns apply → ns1.dnsthing.com → the internet
- Your own relay
- Keep the nameservers you already answer with. dnsthing becomes the control plane in front of them rather than the nameserver itself — the zone files do not change. zones/ → dns apply → your nameserver → the internet
What you stop doing
-
Editing records one at a time
The zone is declared, and apply makes it so. Nothing is clicked into a form that only one browser remembers.
-
Repeating it per domain
Every name is delegated once, to the same relay. A new domain is a file, not a fresh tour of a registrar.
-
Hunting for the one that moved
A bulk change is one command, and its result is the same answer whichever way it is asked for.
-
Wondering what is live
The files are the truth, the relay is the output, and a query tells you which one is wrong.
-
Keeping it in your head
The records sit in a repository like everything else: reviewed, versioned, and undone by reverting.
-
Trusting a console
A zone that is a file can be diffed, tested and rebuilt. A zone that is a panel cannot.
Get in touch
Tell me what you are running and how many names are in it. If a provider gets picked, the first domain goes end to end before anything moves.