Imagine you have to manage DNS for domains spread across multiple DNS providers. You want to apply consistent DNS settings across your zones but the only way is applying the same change manually zone by zone (using multiple control panels). Tedious and a mistake is bound to happen. You want to delegate permissions to other teams but many times the only way is handing out access to everything. If something breaks you have no idea who did it and what exactly was changed.
The existing solution is IaC. Tools like OctoDNS or DNSControl can help you with some of the problems described above. But they require the whole team to feel at home with setting up pipelines, command line tools and git.
With dnswer I want to provide the same level of structure, but in a browser:
- staging / preview before publishing DNS changes (edit and publish are separate roles)
- reusable blocks of records with per-zone variables (not a one-off template: update once, bulk-upgrade every zone that uses it)
- granular access control from full access down to write access on just a single record
- multi-provider sync with drift detection and resolution
- provision new zones at your provider(s), not only importing existing ones
- nameserver verification after changes (verifies that the change is live)
- for providers without an API, a shareable change request with on-demand re-verification (viewable without a dnswer account)
- modern record types (HTTPS/SVCB) and DANE/TLSA for mail, with cert-drift monitoring
- a zone logbook showing what changed, who did it, and why
There are a few ways you can learn more about it:
- Learn: https://dnswer.net/show/ (walkthroughs; annotated screenshots explaining how to use key features)
- Try it: https://app.demo.dnswer.net/ (sandbox with mock providers, free; sign up and verify your email to get in)
If you want to try it with your own zones and API access to your DNS provider(s): I'm looking for up to ten teams (ideally managing 20+ domains across multiple providers) willing to manage real zones using dnswer. Not a big beta: I want to watch how it actually gets used and adapt things quickly. Free for the first 3 months, and early users keep their price for 2 years even after it goes up for new customers. If you're interested, reach out by emailing joost@dnswer.net.
A few things worth knowing before you do. dnswer is not in your resolution path: your records stay at your provider and your nameservers keep answering. If dnswer is down, DNS keeps resolving and you can still change records directly in your provider's control panel, you just lose the workflow on top until it is back. You can leave whenever you like: every zone exports as a BIND file with your record descriptions preserved as comments, so your documentation comes with you. Your provider credentials are encrypted at rest.
I've built it to solve the DNS problems I ran into in the last 20 years. I'd like to learn about other people's DNS problems as well.
Tech stack: Django/DRF, PostgreSQL, NATS, Lit web components, deployed with Ansible.
The existing solution is IaC. Tools like OctoDNS or DNSControl can help you with some of the problems described above. But they require the whole team to feel at home with setting up pipelines, command line tools and git.
With dnswer I want to provide the same level of structure, but in a browser:
- staging / preview before publishing DNS changes (edit and publish are separate roles)
- reusable blocks of records with per-zone variables (not a one-off template: update once, bulk-upgrade every zone that uses it)
- granular access control from full access down to write access on just a single record
- multi-provider sync with drift detection and resolution
- provision new zones at your provider(s), not only importing existing ones
- nameserver verification after changes (verifies that the change is live)
- for providers without an API, a shareable change request with on-demand re-verification (viewable without a dnswer account)
- modern record types (HTTPS/SVCB) and DANE/TLSA for mail, with cert-drift monitoring
- a zone logbook showing what changed, who did it, and why
There are a few ways you can learn more about it:
- Learn: https://dnswer.net/show/ (walkthroughs; annotated screenshots explaining how to use key features)
- Try it: https://app.demo.dnswer.net/ (sandbox with mock providers, free; sign up and verify your email to get in)
- Pricing: https://dnswer.net/pricing
If you want to try it with your own zones and API access to your DNS provider(s): I'm looking for up to ten teams (ideally managing 20+ domains across multiple providers) willing to manage real zones using dnswer. Not a big beta: I want to watch how it actually gets used and adapt things quickly. Free for the first 3 months, and early users keep their price for 2 years even after it goes up for new customers. If you're interested, reach out by emailing joost@dnswer.net.
A few things worth knowing before you do. dnswer is not in your resolution path: your records stay at your provider and your nameservers keep answering. If dnswer is down, DNS keeps resolving and you can still change records directly in your provider's control panel, you just lose the workflow on top until it is back. You can leave whenever you like: every zone exports as a BIND file with your record descriptions preserved as comments, so your documentation comes with you. Your provider credentials are encrypted at rest.
I've built it to solve the DNS problems I ran into in the last 20 years. I'd like to learn about other people's DNS problems as well.
Tech stack: Django/DRF, PostgreSQL, NATS, Lit web components, deployed with Ansible.