Zones & records
A, AAAA, CNAME, MX, TXT and SRV with validation.
Domain & DNSGA
Dedicated DNS, on your own infrastructure
Manage zones and records and deploy Knot DNS on your server in one click — with DNSSEC, resolver and live statistics.
- Knot DNS
- authoritative engine
- DNSSEC
- automatic signing
- < 2 ms
- on the internal network
whycloud.internalLIVE
| Name | Type | Value |
|---|---|---|
| @ | A | 10.20.5.11 |
| api | A | 10.20.2.11 |
| www | CNAME | api.whycloud.internal. |
| @ | MX | 10 mail.whycloud.internal. |
| @ | TXT | v=spf1 mx -all |
Live
HOW IT WORKS
How it works
- 1
Pick a server
Choose any connected server with Docker as the DNS host.
- 2
Choose an address
Listen on an existing IP or add a secondary IP to an interface.
- 3
Create the zone
Knot DNS starts in a container; SOA, NS and ns1 are created for you.
- 4
Manage records
Edit records in the console; changes publish when you apply them.
Capabilities
Domain & DNS
DNSSEC
Zone signing and key management.
Dedicated Knot DNS
Automated deployment on a connected server.
Resolver & cache
Forwarders, cache and organization blocklists.
Health monitoring
Probes, latency and response charts.
Logs & audit
Every record change is traceable.
Geo answers
Different answers for Iranian and international visitors on public DNS nodes (ECS).
USE CASES
Use cases
Internal company DNS
Name internal services like db.corp or grafana.corp without a public provider.
Malware and ad filtering
Network-wide sinkhole with well-known blocklists.
Split horizon
Different answers for internal and public clients with separate zones.
Resilient resolver
Cache with serve-stale for up to 24 hours during restarts.
Technical specs
- Engine
- Knot DNS (authoritative) + Unbound (resolver)
- Records
- A · AAAA · CNAME · MX · TXT · NS
- DNSSEC
- ECDSA P-256 · automatic ZSK rollover · optional NSEC3
- Resolver
- Cache, forwarders, serve-stale
- Sinkhole
- StevenBlack, HaGeZi, OISD, AdGuard
- Monitoring
- SOA probe every 60 s + latency chart
- Logs
- Host journal via the agent
- Deployment
- Container + data volume on the host
Comparison
| whycloud private DNS | Public DNS | |
|---|---|---|
| Where zone data lives | Your server | External provider |
| Internal names | Fully supported | Usually not possible |
| Network sinkhole | Built in | Separate tool |
| Internet dependency | None | Yes |
PRIVATE DNS
DNS that is yours
The DNS service runs inside your network; whycloud only configures and monitors it.
- No dependency on public DNS
- Works in isolated networks
- Deploy on multiple hosts
FAQ
Frequently asked questions
Is whycloud a public DNS?
No; DNS runs on your server.
Is DNSSEC supported?
Yes, zone signing is enabled in DNS settings.
Are query statistics shown?
Yes; blocking and client statistics in DNS graphs.
Does public DNS answer by geography?
Yes; for sites on the CDN, apex records answer with edges of the visitor’s region.
Does it change NS records at my registrar?
No. Creating a zone does not touch your registrar; set NS yourself for public domains.
Can I run more than one DNS server?
Yes. Deploy DNS on several servers for higher availability.
Do record changes cause downtime?
Applying changes currently involves a short restart; the resolver keeps serving cached answers meanwhile.
Turn on your own cloud today
Create an account and connect your first server in under five minutes.