Hacker News new | ask | show | jobs
by nybble41 1496 days ago
Hurricane Electric is great. These days my ISP offers IPv6 via 6rd, but since it's a dynamic prefix (tied to the dynamic IPv4 address) I still maintain the HE tunnel for a static IPv6 prefix while routing most traffic over 6rd. The routing tables get a bit complicated since I can't send packets with the HE source address through the ISP's 6rd tunnel or vice-versa, so I have to route based the source and not just the destination, but overall it works fairly well.

I'm still hoping my ISP eventually offers native IPv6 with a static prefix but it doesn't seem to be a priority for them. On the other hand they haven't gone to CGNAT yet for IPv4—which would break the HE tunnel—so it's not as bad as it could be.
1 comments
puffoflogic 1496 days ago
Depending on what you're actually running at your IP, consider if dynv6.com will work for your dynamic IP. I switched and I've never noticed a difference really. Only one machine on the /64 (or /60 or whatever you have) has to actually ping dynv6 service; it automatically updates the prefix for all other AAAA records. Moreover I've got it set up with a dead simple shell script using curl, no service-specific binaries needed.

Indeed, at this point my only problem is my ISP router will not route the WAN ipv4 address to the appropriate host when the source is on the LAN, meaning I have to use ipv6 to access my public facing server while at home.

link
nybble41 1496 days ago
I have a custom system in place for IPv4 to update AWS Route53 based on this script[0] which I could easily extend to update my AAAA records at the same time, but I prefer a stable IP address. Dynamic DNS (v4 or v6) has a tendency to break down for a time whenever the IP address changes until the old records have expired from resolvers' caches.

[0] https://willwarren.com/2014/07/03/roll-dynamic-dns-service-u...

link