Comment on [deleted]
KISSmyOS@lemmy.world 11 months ago
The modern solution would be buying a domain and pointing the AAAA-record to your server’s ipv6 address.
Comment on [deleted]
KISSmyOS@lemmy.world 11 months ago
The modern solution would be buying a domain and pointing the AAAA-record to your server’s ipv6 address.
TCB13@lemmy.world 11 months ago
… that may change at any time.
KISSmyOS@lemmy.world 11 months ago
If your provider keeps changing your ipv6 prefix, then you still need dyndns.
With a static prefix, you don’t.
Auli@lemmy.ca 11 months ago
No I just have a service that waits for the up to change and when it does it runs a script that updates my AAAA record.
4am@lemm.ee 11 months ago
IPv6 typically assigns blocks to endpoints, not single WAN IPs (ie there is no NAT).
Changing this often would be absolute chaos for all connected devices, even if they’re configured correctly.
TCB13@lemmy.world 11 months ago
Yes ISPs do assign IPv6 blocks via Prefix Delegation, the thing is that Prefix Delegation is over DHCP. They’ll assign a block and if your router/device is restarts they’ll just give you a new prefix. In some even more annoying cases you can even get a new prefix whenever the lease expires.
zaphod@lemmy.ca 11 months ago
Not if you use a Hurricane Electric tunnel for ipv6 transit. My ISP hands out V6 addresses and I still use HE so I get a stable, globally routable /48 that moves with me (I had to switch ISPs recently and I just had to update my tunnel and everything just worked).
TCB13@lemmy.world 11 months ago
True, but that goes back to the irony of “I want to selfhost, and therefore I need a service provider…”, in this case HE. And won’t take of the IPv4 issue, we can’t just assume every network we use to connect to a home setup will be IPv6 capable. At that point you can just pick a Cloudflare tunnel and have it all working.