DynDNS short for dynamic DNS is what you want. But IPv6 only websites are unfortunately even in 2026 still not accessible by many people due to their ISP only supporting IPv4.
this post was submitted on 27 Apr 2026
30 points (94.1% liked)
Selfhosted
61425 readers
708 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
Probably reverse proxy too if it's really unstable
This is how I handle DHCP connections with endpoints, plus I don't want to expose the origin.
curl ip.me and change a varnish config line every 5 minutes if it changes.
I have a $5/mo VPS that my domain points to. It runs caddy reverse proxy to my homelab over wireguard. If my home IP changes, the wireguard 'server' has the the IP of the VPS wg 'client' configured as the Endpoint, with no endpoint set on the VPS. It will switch over pretty quick.
https://anders94.medium.com/wireguard-config-for-the-initiated-2b1cc5f2b1ee
Assuming you are not in a CGNAT, which is common for mobile networks: DNS with low TTL such as FreeDNS, pointing to your IP. And ofc, if you have a router in between, port-forwarding.
Otherwise, a VPN such as Tailscale. But you would need to install it on all your devices.
Otherwise, for HTTP(S) web services, a reverse-proxy such as CloudFlare.
Whoa, FreeDNS is a killer, I wish I knew about it before! I have domains to donate probably (unless they expired lol). I sure need to try that.
Does cgnat even exist for ipv6
DNS is the way around it. But, the caveat is that while you can update your DNS entry as often as you like, itll often be cached on intermediate servers for an unknown amount of time. Expect a downtime of anywhere from a few minutes to days everytime your address changes.
So how does this work then, I host DNS and it pushes my data to other DNS servers around the net every time my IP address changes? Can you share an example of how could be set up?
No, typically you use the DNS server of the domain provider.
Hosting your own DNS server is possible, but if you don't have a static IP address the other DNS servers will have no idea which server to ask when your IP changes, so in this specific scenario it wouldn't work. And in general it isn't really worth it as you get a DNS server with your domain included.
You run a dynamic DNS script. It reaches out to the DNS server (provided by whoever registers your domain name) every five minutes and says "my IP is x.x.x.x".
The problem is that it takes a few minutes to update when it changes. That might not fit your use case.
Unless you set your clients to use the same server for lookups. Then you should get the update nearly instantly.
Tailscale is probably the right move there in that case. Also OS caching may still cause delays.
Assuming reliability is the priority I would suggest going with Tailscale Funnels or a cheap VPS acting as intermediary.
I don't have a lot of experience with dealing with GCNAT, but perhaps you could look into some solution with UPnP or RFC 6887.
When IPv6 was first created, the dream was that your machine would get a new IP address any time the whole network felt some need for that. The idea was, as someone added a network, we may need to change the way your systems are numbered in order to make the backbone routing a lot easier to fit in memory. This hasn't seemed to work out, but that was the dream.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| CGNAT | Carrier-Grade NAT |
| DNS | Domain Name Service/System |
| HTTP | Hypertext Transfer Protocol, the Web |
| IP | Internet Protocol |
| NAT | Network Address Translation |
| VPN | Virtual Private Network |
| VPS | Virtual Private Server (opposed to shared hosting) |
[Thread #258 for this comm, first seen 27th Apr 2026, 09:20] [FAQ] [Full list] [Contact] [Source code]