ALL_POSTS

SEUS DNS Is Here: DNS Hosting Built Into Every Free Domain

2026-10-19

For most of this project's life, step one of getting a free domain was "go set up an account somewhere else first". Pick a DNS provider, learn its panel, add your domain there, then come back and wait for delegation. The name was free, but the road to it had a toll booth made of your evening.

We kept seeing the same thing in support: people got a name, then stalled at the DNS step. Not because DNS is hard, but because a second signup, a second interface, and a second set of jargon is a lot to ask from someone deploying their first page. A free domain that needs three other services taped to it is not really a free domain yet.

So we built our own DNS, and today it ships with every domain we register.

What SEUS DNS is

SEUS DNS is our global DNS hosting and resolution service. When you claim a name, it lands on SEUS DNS automatically. You add records in the same console where you registered, and the name resolves. No delegation to wire, no nameserver dance, nothing to configure anywhere else.

Every record type a real project needs is supported:

  • A, AAAA for pointing at servers;
  • CNAME, ALIAS for pointing at other names, including at the apex;
  • MX for mail, TXT for verification and SPF;
  • NS if you ever want to delegate a piece of your zone;
  • CAA for certificate authority policy;
  • HTTPS, the newer record type that most panels still do not offer.

If you have only ever set an A record before, that is fine. If you want to experiment with the strange ones, that is fine too. This zone exists for learning.

What changes for you

The whole flow is now three steps: search the name in the domain console, verify your GitHub account, add a record. Your domain resolves the moment the record is in. The DNS step did not get easier; it disappeared.

If you already hold a PFS domain

Nothing is taken away from you. Your domain is already on SEUS DNS, and you can manage its records from the My Domains page right now. If anything about the records you had configured matters to you, give them a look and confirm they match what you expect. And if something looks off, tell us: that is exactly the kind of report we want.

One honest note

Running DNS is a bigger promise than handing out names. We know that, and we are treating it that way: resolution is monitored, and the same Acceptable Use Policy that governs domains governs what they resolve to. If you push SEUS DNS to a place we have not tested, we want to hear about that too. Half of the record types in that list exist because someone asked.

If this makes PFS more useful to you, a star on GitHub helps more than you would think. And when you get your first record resolving, stop by the community forum with the #PFS tag and show us what you built.