CoreDNS
on your own machine
CoreDNS is a small, flexible DNS server configured with a Corefile. The egg starts it as a caching resolver that answers only the clients you allow and forwards their queries upstream; most devices only use DNS on port 53, so give the server that port if the node allows it.
$12 a month per machine, with as many servers as it can run. Already on Raptor? It's in your team's Eggs, as software/coredns.
What Raptor does for it
- Backups
- Incremental and encrypted on your machine, every day by default. Restore one file or the whole server.
- Runs on
- x86 and ARM machines, on Raptor's Debian image.
- Every server
- A live console, a file manager with a trash, schedules, crash restarts, alerts, and SFTP. It keeps running if Raptor goes down.
Settings you can change
From the server's Startup tab, without touching a file.
- Version
- The CoreDNS release to install, such as 1.15.0, or latest.Default
latest - Upstream resolvers
- Where queries are forwarded, separated by spaces: addresses such as 1.1.1.1, or tls://1.1.1.1 for DNS over TLS.Default
1.1.1.1 9.9.9.9 - Allowed clients
- The addresses CoreDNS answers, as CIDR ranges separated by spaces; add your own public address as 203.0.113.7/32. Everyone else is refused.Default
10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 100.64.0.0/10 127.0.0.0/8 fc00::/7
From a bare machine
Link your machine
One command on any Debian or Ubuntu box, at home or rented.
Pick CoreDNS
Raptor installs it and starts it, on images it keeps updated.
Open it
At an address your machine comes with, or your own domain.
Made by Raptor and MIT-licensed. Written for Raptor from CoreDNS's documentation, https://coredns.io (Apache-2.0); no upstream egg. Icon: the CoreDNS logo, from https://github.com/coredns. The egg's source.