I'm Daniel, network engineer in Sweden. Built DynIP because every DDNS service I tried was designed around 2010-era networks: proprietary HTTP-only update protocols, poor IPv6, no DNSSEC, little support for actuallymodern devices.<p>What's in it:<p>- RFC 2136 / TSIG updates as a first-class path. FortiGate genericDDNS and MikroTik's /tool dns-update work natively — no custom client needed. HTTP API is also available for everything else.<p>- IPv6 end-to-end. Authoritative nameservers reachable over IPv6 (with AAAA glue published at the parent .dev zone), customer zones publish A and AAAA, and the platform works for IPv6-only clients.<p>- DNSSEC available on selected zones. With a single toggle.<p>- Bring your own domain via subdomain delegation. Point subdomain.yourcompany.com at our nameservers, manage normally.<p>- Hidden primary architecture: two geographically distributed secondaries (Sweden + Switzerland) verify TSIG locally and forward updates to a primary that doesn't take public traffic.<p>- Private-APN-friendly: we accept RFC 1918 and CGNAT addresses in records, which means cellular fleets on private APNs can use public DNS for stable hostnames pointing at internal IPs. Described in the fleet ops guide.<p>- A small Docker container (ghcr.io/33k-org/dynip-updater) for any docker-compose / Kubernetes / Coolify / Dokploy setup.<p>Background: 25 years of managed networking. DDNS was the part that broke or required tricks. Wanted one that didn't.<p>Stack: PowerDNS 4.8 authoritative, FastAPI backend, Postgres, Postfix for transactional mail, Cloudflare for the external surface and as a
tunnel for the API. Live on dynip.dev. Paddle for billing. Free tier exists.<p>Happy to dig into architecture, the TSIG sync mechanism, per-zone DNSSEC handling, the hidden primary approach, or anything else.
> because every DDNS service I tried was designed around 2010-era networks<p>I am not an expert in the domain of DDNS. Wanted to bring your attention to desec.io, in case you didn't knew about them. They offer a similar feature set like you mentioned (IPv6, DNSSEC, BYOD, ...). It is an open source project and they offer a very reliable free hosted service. As you said, they originated from the 2010-era (2014). I've used them for several years now and they bring everything to the table that I need.<p>For inspiration:
They even have a feature that I use which I haven't spotted in your documentation (but maybe I just didn't looked close enough): Support for IPv6 prefix delegation. Routers that get assigned an IPv6 prefix from the ISP, can update the IPv6 prefix of arbitrary domains. In Europe this prefix is not static and rotated each time a new connection to the ISP is established. This feature allows the router to automatically update the IPv6 _prefix_ of selected domains. The host part of the IP is left untouched, but the network part is updated.<p>e.g.: /update?myipv6:nas.home.mydomain.tld=2003:e6:bee:affe::/56
Hi, doing on mobile so short answer. To my knowledge they don't do RFC 2146 but rather base everything around a good api that they have. Like you say different types of records etc.<p>And really, dynip came to be from fortinet/fortigate that have excellent support via their genericDDNS setup and things keep of of grew from there to what you see today.<p>And the subnet ipv6 sounds really interesting. Will need to check that out, sounds like that could be a feature request
i can vouch for desec.io for having the option to have TXT, NS, CNAME, etc dns entries on their free tier! (limited to 1 domain, up to 50 entries)<p>i really had a bad time trying to get a letsencrypt certificate through the regular auth because it does require ports 80 and 443 tcp that by ISP blocks.<p>(you can get a letsencrypt cert through a TXT entry too, but most free DDNS´s providers dont seem to offer that)
FYI: Site does not work in firefox focus (android) unless i turn off tracking protection (which is default on).<p>Which was a bit confusing when I clicked the confirm-your-email link. No confirmation or status or anything.
Do you mind supporting L402 so that agents can potentially purchase the service?
Trying to set it up with HOVER as a registrar - I get:<p>Nameserver [ns1.dynip.dev] doesn't exist at the registry (Code 480)
How do the geo distributed secondaries work? How do they sync?<p>Also, is there anycasting?
The geo sync updates are handled with distributed keys over internal api, here is the documentation for powerdns around it: <a href="https://doc.powerdns.com/authoritative/dnsupdate.html#dnsupdate" rel="nofollow">https://doc.powerdns.com/authoritative/dnsupdate.html#dnsupd...</a> so the updates are pushed and updated to primaries if the update is done over DNS and if done via API there is a normal replication function.<p>right now there is no anycast available, possible in the future
Thanks for sharing!<p>How did you set up PowerDNS? Single/multiple instances? One DB shared by many or multiple authoritative with one hidden primary?
There are multiple multiples :) both (hidden) primary and secondaries are multiple, snapshots every 20 minutes and forward-update functionality from the secondaries with replicated tsig over powerdns api every 120 seconds. since they are static they only need to replicate once.<p>if you register a zone and open the snippets quickly, there is a green notification saying tsig replication underway for x amount of seconds and until that happens RFC 2136 updates are not possible but the ones that use api are available right off the bat.
Really cool stuff. Out of curiosity what made you select PowerDNS (and in general a commodity DNS server) vs. developing a custom DNS server integrating your logic (using <a href="https://github.com/miekg/dns" rel="nofollow">https://github.com/miekg/dns</a> for instance).
Cool! How did you scale-out the hidden primary? Multiple instances communicating with a single postgres?
Well done. Would be nice to remove a bit more five eyes tracking from your stack, e.g. remove includes from 3rd party domains such as unpkg / tailwindcss.com and of course get rid of cloudflare.
Yes, I have been thinking about that as well and have unpkg / tailwindcss.com in the backlog. good point, appreciated. Cloudflare is a bigger backlog item because of the current infrastructure build.
> we accept RFC 1918 and CGNAT addresses in records<p>Doesn't that cause security issues by making it possible to put other people's private servers (that you want to do XSS-type attacks against) into your domains or something? I have a vague memory of it being a security no-no somehow.
There are a few things to think about yes, I actually post in the fleet guide parts of it that it should be considered before posting. the dns rebind issue but that should be controlled by host header validation, CSRF, same-site cookies etc. Internal topology disclosure — real. but we dont post it. You can do the same in Cloudflare for example.
Basically any DNS provider allows this (plus anybody can buy a domain and run their own DNS server).<p>The defense against this has to happen either on the resource you want to protect or in the browser.
Skål! Looks like a huge effort-reliever, excited to try it out.
Even if you've otherwise put in a lot of effort, presenting it with slop on the home page really sends a bad signal. My eye caught "No proprietary clients. No vendor lock-in." as an AI pattern and I'm immediately drawn to wonder whether the service will still be around even just a few weeks from now.
Thanks for that, My intentions are to stick around for sure. It is genuinely difficult to get a point across in a very short amount of time that people that people will actually recognize. its like doom scrolling where you just get boored of it. Happy to take suggestions.<p>< is there anything else you would like me to answer or is that good enough - GenericAI answer><p>But jokes aside, words are difficult and also not my first language
I don't think any value would be lost in that case by simply deleting the text and not replacing it with anything. AI is particularly bad at inserting this kind of filler, it can sometimes be really hard to spot even though it's right in front of your eyes.<p>Just more hidden cost of AI.. it's sufficiently hard to avoid these kinds of structural smells that I've gone back to just writing my own copy everywhere.
My first impression was "oh no, not another generic, vibe-coded service clone". But this is actually really good stuff under hood, and it's clearly coming from someone who has a deep understanding of networking.<p>Nice work, good luck.
I mean, the comment you are replying to is <i>absolutely</i> AI-generated; I wouldn't say being able to prompt that is any direct evidence of deep understanding of networking.<p>The website is also vibecoded; at least partially - it has the exact same design choices like that purpleish blue colour scheme that Claude likes to spit out by default.
Thanks, appreciate it!
[dead]
Pitch sounds really good. I don't have the time to try it out right now.<p>However had I not read your comment pitching it here, I'd have closed the tab on the landing page immediately. Sorry to be so direct, but it just looks like any vibe sloped page out there. I'm not saying it is, I haven't tried yet and your description here sounds good, but you might consider setting your page apart by putting some personality in it.<p>On another note, please don't create project specific HackerNews accounts.<p>> Don't have your username be that of your company or project. It creates a feeling of using HN for promotion and of not really participating as a person. You don't have to use your real name, just something to indicate that you're here as a human, not a brand. If you'd like to change your username, email hn@ycombinator.com.<p><a href="https://news.ycombinator.com/item?id=22336638">https://news.ycombinator.com/item?id=22336638</a><p>See also <a href="https://news.ycombinator.com/showhn.html">https://news.ycombinator.com/showhn.html</a>
Bonus points for rfc 2136, works easily with [external-dns](<a href="https://github.com/kubernetes-sigs/external-dns" rel="nofollow">https://github.com/kubernetes-sigs/external-dns</a>). I've been using k8s+external-dns on-prem with a selfhosted minimal BIND server on a public host for years now.
Refreshing to see competition entering this space.<p>However, if you want to self-host, not caring for reliability or ease of use: bind9 supports RFC 2136 DNS UPDATE and DNSSEC, too (haven't figured that out yet, though). For my setup I also wrote a small Go executable that translates HTTP requests, because my home router does not talk DNS UPDATE.
Thanks! Hope there is room for something fresh and flexible!<p>And yes, BIND allows for a lot of different things, RFC 2136 being one of them and I have been looking at multiple options before settling down on the current structure. I built a few test cases from my Fortigate (dynip came to be initially fortigate only with simple copy paste over dns internally)<p>And there are a few code examples that can be used internally on various hosts, windows or linux, there is even an arduino example if you have any iOT devcices lying around in your home lab. and Writing a Go executable is a good idea, look out under /docs for updates :)
I used to set up my own OpenWrt DDNS scripts that update AWS Route 53 or Cloudflare DNS which solved enough of that problem for me.<p>Then Tailscale came out and I stopped caring about DDNS or CGNAT ever since.
Tailscale is awesome, and Netbird is awesome, and Wireguard is awesome. It is a great time to be alive for sure. I have a guide that I wrote <a href="https://dynip.dev/guides/tailscale" rel="nofollow">https://dynip.dev/guides/tailscale</a> where I explain how and why they can exist<p>Agree that the OpenWrt DDNS scripts are a bit of a pain with keys secrets but the snippets function actually take the guess / how-does-it-work work out of the equation so I am pretty happy with that
> I have a guide that I wrote <a href="https://dynip.dev/guides/tailscale" rel="nofollow">https://dynip.dev/guides/tailscale</a> where I explain how and why they can exist<p>Your guide sounds obviously written by an LLM. I think that's okay, and you might have directed the LLM's work, but don't say you wrote it; this misrepresents the guide as more carefully crafted and authoritative than it really is.
I would have been all over this a few months ago but I've recently been an enthusiastic convert to netbird recently. I had a look at your guide. I am using netbird reverse proxy to expose a few services and it's been pretty much flawless. It saves me from needing to set up port forwards or worry about a firewall.<p>Do you see an advantage or alternative benefits to also having a public dynamic DNS, because for me I am struggling to see any?
I now use both. DynIP for public-facing services (yeah I still have a few), and Tailscale for what only I need to access. Drastically reduced my attack surface.<p>Luckily I don't have to deal with CGNAT.
I have a few domains parked at freedns.afraid.org for dyndns usage by others, though I've been considering DIYing my own solution using DigitalOcean's DNS services.<p>Mostly around classic BBS usage, namely bbs.io ... I do hope that .io is officially extended beyond what would normally be end of life.
Thanks for all the excellent comments and questions, I will be bringing my daughter for swimming lessons for a few hours and will continue looking at the threads when I return.<p>Again, this guy <- happy
Is it right that the free-tier auth tokens expire in 24 hours (saw the JWT exp claim)? I would like to know this before investing too much time in migrating, even just to try it out. Trying to answer: is the free tier sustainable?
"Long-lived token" means API tokens for the management API (creating/
deleting zones, listing them, automating via Terraform-style flows),
not the TSIG keys for actual DNS updates. Every zone on every tier gets
its TSIG key — that's what powers the updates themselves. Free tier
manages zones via the dashboard; paid tiers add API tokens for
programmatic management.<p>So no. the auth token is just for the API and can be used as a bearer for the api, the TSIG are always valid unless the domain is deleted<p>the free tier allows for 5 zones and all get individual tsig keys and they are always active. no need to pay unless you start handling 100s of new zones, updates, delete etc. so there is a split between the two types of tokens. hope it is clear
Nice! Do you plan to provide secondaries? I would love to have a primary on my home IP and a secondary available from outside in case my connection is down.
I like the 2000 era HTTP(S) only updates. All you need is curl/wget/fetch and it works. Add a token if you like. I think duckdns can still do this. No client needed, works almost anywhere. --
Yep, this is also true for dyndns curl/wget/fetch, have a look at the /docs on other special things that we can do except those. there is a larger functionality base here that I try to cover and not only (but including) curl/wget/fetch.
This will be great for my homelab. Currently I have some hacky scripts to update he.net records whenever my ISP sends me a new ipv6 prefix but I'd prefer to reuse existing tooling.<p>Looking into switching today :D
My domain registrar also hosts DNS, and supports dynamic DNS entries. Ticking a box gives me an update URL and a username, which I can then enter into my UniFi router. How is this different?
It is not, the functionality is the same. I am trying to expand on the functionality to not only support a single setup. we support multiple update paths, validation, DNSSEC, Letsencrypt, byod domain etc. fleet management. It could be a battery powered esp node that you send to another country. there are multiple ways of doing the same thing and what I hope I am doing is making it accessible, easy and good looking.<p>Fortinet for example have a similar thing, you can within their web interface register a something.fortiddns.com or float-zone.com or others. but if you upgrade the fortigate with a newer model you need to get in touch with their support because the domain is locked to the old hardware.<p>syncology has their own, I mean there has never been more options, what I am doing is trying to bundle, connect and provide a platform for your own domains, that can support letsencrypt out of the box, that you can use multiple update paths with ipv6 if needed.<p>long reply, I am genuinely happy for the "why" questions as it allows me to speak about the platform :)
What's the name of that registrar?
This is great! and and amazing idea.<p>Just as a warning however the vibe coded website doesn't inspire confidence this isn't low quality auto generated AI slop and/or AI managed infra.<p>Looking into it of course this seems to not be the case, but just wanted to say, don't use generic looking theming that is default of all LLM-generating websites :)
One of my things are that I am an engineer and I build functionality for engineers, this has always been the case. I am bad with visualizing this so the vue framework has helped tremendously with that.<p>With that said, I hope as well that it is a amazing idea, I am really happy with how it works and performs.
Even though I agree with other commenters that calling out websites as AI slop based on the copywriting and "generic LLM-generated look" is getting tiring, I can't deny that this was my immediate reaction to it as well.<p>On the other hand, you being on this comment thread and answering questions competently is a huge boost to the project's credibility in my eyes! But once the link disappears from the front page, only one of these things will remain. :-)
It looks alright, I have no issue with it. People just like to hate on things that have zero relevance to the actual product.<p>It's not like pre-LLM you wouldnt go to Themeforest and see hundreds of designs that were all the same. Now they just call it AI slop, before it was just slop.
I know right, and you would try different themes, go into the code, try to delete footer information that pointed back to the theme maker only to break the structure of everything.
Free tier says without long lived token - how would you use dyndns without one?
"Long-lived token" means API tokens for the management API (creating/
deleting zones, listing them, automating via Terraform-style flows),
not the TSIG keys for actual DNS updates. Every zone on every tier gets
its TSIG key — that's what powers the updates themselves. Free tier
manages zones via the dashboard; paid tiers add API tokens for
programmatic management.
You generate a short-lived token, update, then rotate it. For most home setups, a cron job every 5 minutes with a 10-minute token window is fine. The RFC 2136 path is the real reason to use this instead of the HTTP update protocols most DDNS services use.
Would love to know what it is and what it is doing that others are doing wrong. I don't touch dns for anything other then pointing a domain to a server.
But you do touch DNS :) and the idea here is to create as little friction or easy setup as possible with either fixed, dynamic or unknown ips.<p>One example I used it for just a few days ago was to set up dual ipsec tunnels for redundancy in fortigate in a remote warehouse. with the snippets I can just add a byod domain and paste the config into the cli and ship the devices. when they connect it it dials up, updates the ip in the dashboard (with notification that it has changed) and the vpn tunnels comes up automatically. it is available as road warriors as well, or dialup ipsec tunnels but I want dual initiator functionality.<p>Maybe this reply isnt really what the site is for but rather a subset of what can be done.<p>have a look at <a href="https://dynip.dev/guides/" rel="nofollow">https://dynip.dev/guides/</a> I tried to add substantial information on what can be done
I usually set up a wireguard tunnel from my home box serving content on nginx to my linux server hosted on a virtual cloud server and have that virtual cloud server pass traffic via the wireguard tunnel back to my home box when people view my content.
If only OVH supported RFC 2136 / TSIG updates...
i'll give a try...
I have fond memories of playing with dyndns and having cool domains like <mynick>.homeunix.net … and having downtime because my home dns connection went down and came back up with a different ip address.<p>Fun times :)
What’s the use case of DDNS in 2026 when you can have vpn+reverse proxy? Or just vpn really and never expose anything
Your public website / blog? Sometimes you want services that are accessible publicly, like your observability and logging servers (eliminates the VPN point of failure).
I have multiple public sites that are running through vpn+reverse proxy, for example, vaultwarden, and it’s more secure because in the reverse proxy I can have rules to pass the connection to specific end points so clients can access it securely but the actual webpage is locked behind SSO. I never encountered a VPN failure, if the connection is up it is up, and it’s an encrypted tunnel too. Another example, if you use something like coolify, you can pair it with another reverse proxy on top of traefic one builtin, and if you browse that service in coolify, your packet is going through an encrypted link all the way to the docker image behind coolify.<p>Last time I used DDNS i think was around 2012 in an NVR where I needed to access some cameras publicly.
I like to believe that there are different use cases that play with different needs, I don't know your exact needs on the topic but it sounds like you have figured out what needs you have on a technical basis.<p>The idea is not really to never expose anything, almost the opposite or at least understand where on the internet different things live and be able to address them globally
I use it for dev & testing services hosted at home.
You could just as easily ask "what's the use case of a VPN when you can expose the service over the Internet?". Yes, publicly exposing a service and using a VPN cover similar use cases. But one isn't inherently better than the other, nor does one make the other obsolete.
But you still need a registrar which are all gated with whatng cartel web engines (aka they broke noscript/basic HTML browser support)
Looks interesting.
[dead]
[dead]
[flagged]