SEUS DNS is nine days old, and it already answers for every domain this project has registered. Two things were planned for it from the start, and both are live today: an anycast network that answers queries from the nearest node, and open doors for domains you registered somewhere else.
What anycast actually changes
A DNS query is a round trip, and the distance used to be whatever it was. With anycast, a.ns.fs5.net and b.ns.fs5.net are announced from more than 36 locations around the world at the same time, and internet routing delivers every query to whichever one is closest. A visitor in Singapore and a visitor in Berlin each get their answer from a machine near them, and neither of you configured anything.
Credit where it is due: SEUS DNS runs on bunny.net's anycast DNS backbone, the same network that powers their own DNS platform. It spans six continents and 77 countries, sits on Tier 1 transit with DDoS protection at the edge, and keeps answer latency below 20 ms in most regions. We did not pour the concrete, and we are not going to pretend we did. We picked a serious partner, moved every zone onto it, and watch the answers come back.
That does three things worth caring about:
- Latency drops. The nearest node answers, so lookups finish faster, and page loads feel it, since DNS sits at the front of every visit;
- The service gets tougher. If one node has a bad day, routing steers traffic toward the healthy ones instead of dropping queries on the floor, and the edge absorbs junk traffic before it reaches your zone;
- Record changes go live fast. Every node serves the same data straight from the console, so the record you save is answerable worldwide almost immediately.
One honest caveat: resolvers around the world still cache answers for their TTL, so a few visitors may see an old record briefly after you change one. That is how DNS works everywhere, and it was true yesterday too. Lower the TTL before a planned change if you want it to spread quickly.
Bring your own domain
Here is the part that opens SEUS DNS to the rest of the internet. Until today, the only zones it served were PFS domains. As of October 28, 2026, any domain you own can join, wherever it was registered.
Point your domain's NS records at our nameservers:
your-domain.example. NS a.ns.fs5.net.
your-domain.example. NS b.ns.fs5.net.
Once your registrar publishes the change, your zone lives on SEUS DNS: the same record types (A, AAAA, MX, NS, CAA, TXT, CNAME, ALIAS, HTTPS), the same console, the same anycast network. You stay in control the whole time. The delegation lives in records at your registrar, so you can point the domain somewhere else whenever you like, and it follows you out with no lock-in.
The same Acceptable Use Policy applies to a domain you bring as to a domain we handed you. It is the same network and the same community; the rules do not change with the registrant.
If you already hold a PFS domain
Nothing to do. Your nameservers were already a.ns.fs5.net and b.ns.fs5.net, and those are exactly the addresses now announced from every node. Your visitors are already being routed to the nearest one, and not one of your records changed.
What to watch for
The network keeps growing without us lifting a finger: bunny.net lights up new locations regularly, and SEUS DNS inherits every one of them. We will post notable coverage changes in SEUS Community as they land. We are also watching resolution the way we promised to. If lookups feel slow, or your zone answers oddly from where you sit, tell us; the first weeks of an anycast rollout are exactly when we want sharp eyes on it.
Thank you
SEUS DNS got built because this community kept asking for a DNS step that did not hurt, and it keeps improving because you report what you find. If you bring a domain of your own over, write down how the move went and post it in SEUS Community with the #PFS tag; migration notes are the posts we read first. And if this project keeps being useful to you, a star on GitHub helps the next learner find us.