Comparison
PNTR vs Duck DNS
Duck DNS does one thing extremely well: it keeps a hostname pointed at a home connection whose IP address keeps changing. That is dynamic DNS, and PNTR does not do it — there is no update endpoint for a router or a cron job to call. If your IP changes, this comparison ends here and the answer is Duck DNS.
PNTR compared with Duck DNS
| Feature | PNTR | Duck DNS |
|---|---|---|
| Dynamic DNS (IP updates from a client) | Not supported | Yes — this is the core feature |
| Router and NAS integrations | None | Widely supported, including a first-party Home Assistant add-on |
| Subdomains per account | 1 as a guest, 3 free with GitHub, 15 on Premium | 5 |
| Record types | A, AAAA, CNAME, TXT, MX | A, AAAA, and TXT |
| Request capture | Included | None |
| Catch-all email inbox | Included | None |
| MCP server for Claude / Cursor | Yes — dev.pntr/pntr in the official MCP registry | None published |
| Cost | Free tier, optional $5/month Premium | Free, funded by donations |
Duck DNS pricing and limits last checked on . Check their site for current terms.
Choose PNTR when
- Your target is a fixed address — a cloud host, a Vercel or Netlify deployment, a CNAME to a platform.
- You want request capture or an email inbox on the hostname, not just an address record.
- You want to manage records from a script, CI, or an AI assistant.
- You need MX or CNAME records, which Duck DNS does not offer.
Choose Duck DNS when
- Your IP address changes. This is the deciding factor — PNTR has no dynamic update endpoint, so a home connection would drift out of date and stay broken.
- You are pointing a hostname at a homelab, a NAS, or a self-hosted service behind a residential connection.
- You want something that already integrates with your router, Home Assistant, or an existing ddclient setup.
- You want a service with a very long operating history and an enormous installed base.
Questions
- Can PNTR be used for dynamic DNS?
- Not properly. You could script a record update through the API on a timer, but there is no purpose-built update endpoint, no client support, and nothing designed for it. If your IP changes, use a dynamic DNS service.
- Can I point a PNTR subdomain at my home server?
- Yes, if your IP is static or effectively static. If your ISP rotates it, the record will go stale and PNTR will not notice.
- Does Duck DNS support CNAME or MX records?
- No. It handles A, AAAA, and TXT records, which covers the dynamic DNS use case and the TXT records needed for Let's Encrypt DNS-01 challenges.
- Which should I use for Let's Encrypt wildcard certificates?
- Both can hold the TXT record a DNS-01 challenge needs. Duck DNS has more documented tooling for this in homelab setups; PNTR lets you set the record over its API.