Subdy documentation
Human-readable subdomains with real DNS, wildcard TLS and dyndns.
Subdy gives every server you run a name: myapp.subdy.io instead of
203.0.113.7. Underneath it is an authoritative DNS network you control
through a dashboard, a REST API, a dyndns2 endpoint and an MCP connector
for Claude.
Where to start
- Quickstart — from zero to a resolving subdomain in about five minutes.
- API reference — every endpoint with a copyable,
verified
curlexample. - MCP connector — manage your DNS by talking to Claude.
What you get
| Area | Included |
|---|---|
| DNS | A, AAAA, CNAME and TXT records, wildcard names, TTL from 60s |
| TLS | Wildcard certificates via Let's Encrypt, auto-renewed (Pro) |
| dyndns | GET /nic/update — works with routers and NAS out of the box (Pro) |
| API & MCP | Bearer-token REST API and an MCP server for Claude (Pro) |
All example IPs in this documentation come from the reserved
documentation ranges (203.0.113.0/24, 198.51.100.0/24) — replace
them with your server's address.