nsrecord.net

Wildcard DNS for any IP address — and delegation to a nameserver at that IP. Free, no signup, nothing to configure.

Any hostname containing an IP address under nsrecord.net resolves to that IP, sslip.io-style. But the reason this service exists as a separate fork: under the handoff.nsrecord.net zone, put labels in front of the embedded IP and nsrecord.net delegates that subtree to a nameserver running at the IP itself. Run any DNS server on your box and you own an entire delegated namespace — any record type, no domain registration, no zone file edits.

The code can root delegation at any subdomain you configure — or the whole domain. handoff.nsrecord.net is simply where this hosted instance scopes it; everywhere else under nsrecord.net is plain IP-echo DNS.

QueryResolves to
192-168-1-10.nsrecord.net 192.168.1.10 dashed form
192.168.1.10.nsrecord.net 192.168.1.10 dotted form
myapp.10-0-0-5.nsrecord.net 10.0.0.5 any prefix you like
2a01-4f8--1.nsrecord.net 2a01:4f8::1 IPv6 (dashes for colons)

Delegation: bring your own nameserver

On this hosted instance, delegation applies under handoff.nsrecord.net. Within that zone, what happens depends on how many labels sit in front of the embedded IP:

QueryAnswer
0 labels 192.168.0.1.handoff.nsrecord.net A → 192.168.0.1 — classic sslip.io behaviour, unchanged
1 label example.192.168.0.1.handoff.nsrecord.net A/AAAA still resolve directly to the IP; an explicit NS query returns NS → 192.168.0.1.handoff.nsrecord.net with glue
2+ labels deep.example.192.168.0.1.handoff.nsrecord.net every query type returns a referral to the nameserver rooted at the IP — your server answers

So if a machine at 203.0.113.7 runs a DNS server, everything two or more labels deep under 203-0-113-7.handoff.nsrecord.net is answered by that machine: TXT records for ACME DNS-01 challenges (real wildcard certificates on lab and internal hosts), CNAMEs, MX, SRV — whatever your nameserver serves. nsrecord.net is just the always-there delegation root.

Try it

$ dig +short 192-168-1-10.nsrecord.net
192.168.1.10

$ dig NS example.192-168-1-10.handoff.nsrecord.net
;; …NS → 192-168-1-10.handoff.nsrecord.net (glue: 192.168.1.10)

$ dig TXT anything.example.192-168-1-10.handoff.nsrecord.net
;; referred to — and answered by — the nameserver at 192.168.1.10

How it works

nsrecord.net runs metahertz/sslip.io, a fork of Brian Cunnie's excellent sslip.io — the open-source Go DNS server that parses the IP address out of the queried hostname and answers with it. The fork adds the subdomain-delegation behaviour above: NS referrals (with glue) that point at the query's own embedded IP, rooted at whatever subdomain you configure. Self-host it and you can delegate under any name — this public instance confines delegation to handoff.nsrecord.net. If you only need plain IP-echo DNS, the public sslip.io service is the canonical choice; all credit for the original software goes to that project.