NoDNS.shop

Your domain.
No registrar needed.

Register a .nodns.shop subdomain instantly. Pay with Cashu sats. Records propagate via Nostr in seconds.

e.g., alice.nodns.shop

1-3 chars 200 sats·4-6 chars 20 sats·7+ chars 4 sats

What is NoDNS?

NoDNS is a protocol that resolves DNS records from Nostr events. Instead of registering domains through a traditional registrar and configuring DNS through a control panel, users publish cryptographically-signed events to Nostr relays. A NoDNS-compatible nameserver reads these events and serves them as standard DNS responses.

No accounts. No passwords. No billing. Your Nostr keypair IS your domain credential. Anyone with a Nostr key can claim a subdomain under nodns.shop and point it anywhere they want.

Custom names like alice.nodns.shop are possible through cryptographic delegation. A zone registrar signs a Nostr event granting a pubkey exclusive control over a human-readable name for a time period. This delegation is irrevocable— even if the registrar removes the DNS records, the Nostr event remains the authority.

Decentralized

No central authority controls your records. Your private key is your proof of ownership. No one can take your domain or modify your records without it.

Instant

Publish an event and your DNS records propagate globally in 3-5 seconds. The bot subscribes to relays in real-time and pushes changes via DDNS immediately.

Standard DNS

Queries resolve via normal DNS protocol. Any resolver, any operating system, any device. No special software needed to look up records.

How It Works

1

Generate Keys

Create a Nostr keypair. Your public key (npub) becomes your domain identifier under nodns.shop.

2

Publish Event

Construct a kind 11111 Nostr event with your DNS records as tags. Sign it with your private key and publish to relays.

3

Bot Processes

The nodns-bot subscribes to relays, validates your event, checks policy rules, and pushes records to the authoritative DNS server via DDNS.

4

DNS Resolves

Within seconds, your records are live. Standard DNS queries return your published records. Zero special software needed on the resolver side.

DNS Record Browser

Browse all DNS records verified from three independent sources

Live Event Feed

See more →
Connecting to relays...

Publish Pipeline

1 / 4
1
Publish Event
2
Bot Validates
3
DDNS Update
4
DNS Resolves
kind: 11111
tags: [["record", "A", "@", "185.18.221.10"]]
Try It Yourself

FAQ

How long until my records are live?+
Typically 3–5 seconds from publishing your Nostr event. The bot subscribes to relays in real-time, validates the event, and pushes changes via DDNS immediately.
What should I put in the name field?+
The name field is the subdomain label only. Use @ for your root domain (npub1abc...xyz.nodns.shop), or a single label like www or blog for subdomains. Never put a full domain path — the bot constructs the FQDN automatically.
How do I get a human-readable domain like alice.nodns.shop?+
Human-readable names require cryptographic delegation from a zone registrar. A registrar publishes a delegation tag assigning a name to your npub for a fixed period. Watch the roadmap for public availability.
Can I publish records for a different zone?+
No. Each zone has its own nodns-bot instance. Publishing to the nodns.shop bot only creates records under *.nodns.shop. Other zones need their own bot infrastructure.
Why is my record showing up as a long nested domain?+
You likely put a full domain path (like blog.alice.nodns.shop) in the name field instead of a simple label (blog). The bot appends .{your_npub}.{zone} automatically. Use just the subdomain part.

More questions answered in Learn →