Own bob.rxd,
manage bob.rxd.zone.

Lets verified owners of a Radiant Wave Name manage public DNS records for their namespace — point at GitHub Pages, Vercel, or Netlify with a CNAME, get a real SSL certificate, no shared registrar required.

Connect Wallet Verify Radiant Name

How the mapping works

Owning a single Radiant name gives you full DNS control over its zone. bob.rxd unlocks A, AAAA, and CNAME records anywhere under bob.rxd.zone — add @, www, test, api, or any other hostname, no separate registration needed per subdomain.

bob.rxdbob.rxd.zone

bob.rxdwww.bob.rxd.zone

bob.rxdtest.bob.rxd.zone

Official Radiant sites

Verified against on-chain ownership — every other rxd.zone subdomain is run by an independent name owner. See the full list.

demo.rxd.zone

Building something with logins on your subdomain?

Until rxd.zone is on the Public Suffix List, browsers treat all its subdomains as one "site" - so cookies need extra care. It's two rules, and they're easy: read the security guide.

Ownership-verified

Every write is checked against Radiant ownership before it ever reaches PowerDNS.

Server-side only

The PowerDNS API key never leaves the server. All writes happen through audited API routes.

A, AAAA & CNAME

Host on GitHub Pages, Vercel, or Netlify with a CNAME, and get SSL via a scoped ACME TXT challenge - no MX, NS, or wildcard surprises.

Namespace isolation

bob.rxd can never touch another owner's zone, rxd.zone itself, or the nameserver records.

Own bob.rxd,manage bob.rxd.zone.

Own bob.rxd,
manage bob.rxd.zone.