the part of dyndns nobody wants to run
Your service moves.
Its address shouldn't matter.
dnslet is the domain, the account, and the DNS record behind your dynamic DNS setup — the piece most people put off because it's fiddly to get right. Request a subdomain, point almost any ddns agent at it, and your service stays reachable — over IPv4 and IPv6, both.
$ dig +noall +answer home.yourname.dnslet.com A AAAA
;; ANSWER SECTION:
home.yourname.dnslet.com. 203.0.113.42 A
home.yourname.dnslet.com. 2001:db8:85a3::8a2e:370:7334 AAAA
What's a dnslet?
A dnslet is the domain, the account, and the DNS record that most people quietly avoid setting up themselves — a static Fritzbox rule, a half-finished ddclient config, a subdomain nobody renewed. You only have to do two things: request the domain, and run (or let run) the small component that keeps its IP address current.
How it works
Request your domain
Ask for a subdomain and an account. That's the only setup step that's actually yours — the domain, account, and DNS side is what dnslet takes off your plate.
Let a component update it
Run the small dnslet agent, or point an update client you already run — ddclient, inadyn, a router's or NAS's built-in updater — at the dnslet endpoint.
Your name resolves
your-name.dnslet.com answers with the current address — A and AAAA both — anywhere, with any client, over plain DNS.
Works with what you already run
The dnslet endpoint speaks the same update protocol most dynamic DNS agents already expect. If you've got ddclient, inadyn, or a router or NAS with a built-in dyndns updater, point it at dnslet instead of standing up your own DNS side.
No existing agent? Run the small dnslet component instead — it does the same job, watching your address and reporting changes, over IPv4 and IPv6.
Where it earns its keep
Reach your own apps, without building dyndns yourself
Access services hosted in your own environment — a NAS, a media server, an internal tool — from anywhere, without setting up the domain, account, and DNS record chain on your own.
Nodes that come and go
Point one subdomain at whichever edge box, Raspberry Pi, or short-lived VM happens to be doing the work right now.
Bookmarks that don't rot
Keep scripts, monitoring, and RDP or SSH shortcuts pointed at a name instead of an IP you have to go look up again.
One name, several environments
Move a service between a home rack and a cloud box without telling anyone downstream — the record just follows it.
Or skip the setup entirely
Requesting a domain and pointing an agent at it is already the short version — but if you'd rather not touch even that, there's a service offering to get your whole dyndns setup done for you: the subdomain, the right agent for your environment, and the update running. You just get a name that works.