On Tuesday January 04 2022 15:49, you wrote to me:
MvdV>> I had no problems since I got native IPv6 fom my provider six years MvdV>> ago. I only had problems with the he.net tunnel. The SixXs tunnel MvdV>> gave no problems.
SixXs used "local" POPs and the prefixes allocated were taken out of the block assigned to the ASN that ran the POP servers. My POP was located in Ede, just 30 km frome here. So no problems with geolocation.
AN> I did not use SixXs, but it stopped its service anyway some years ago.
I used their tunnel until they stopped in june 2017.
AN> The he.net tunnel ran fine for many, many years - and I had my fixed AN> prefix where I even could provide my reverse DNS for.
I ran the he.net tunnel in parallel with the SixXs tunnel for a couple of years.
AN> The native IPv4+IPv6 connection from Telekom does work, but as it's AN> only a consumer-grade connection, I don't get fixed addresses or a AN> fixed prefix. But I found a workaround using Dynv6 :)
I never understood why providers still issue dynamic adresses to their customers. It made sense in the time of dial up. But now with "always on" connections...
Anyway, I too have a dynamic IPv4 address and a dynamic IPv6 pefix. But in practice it is semi static. It does not change often enough to invest time and energy in automatic updates.
AN> So my router (Fritz!Box) calls a script on one of my rented vServers AN> (via a https request), which in turn sets the IPv4 address and the AN> IPv6 prefix on Dynv6 and on my own DNS zone. And it seems to work fine
