as far as i understood it the first 4 blocks of my public ipv6 still change from time to time when my ISP tells it to which i can keep up to date with my DDNS but not too sure if theres not a work around anyway i already got the duckdns domain for my npm so that i can get SSL certs from lets encrypt and dont have to worry abt self signing anythingAt which point you shouldn't need DDNS as it is not tracking anything.im pretty new could be wrong but i just set up the wg-easy wireguard image in a container and it was a big hassle since my ISP uses CGNAT so i dont actually have my own public IP might be ur case as well hence a different IP is shown to every server u ask for ur IP than u think it should. either way my solution in the end was forcing duckdns (which im using for dynamic dns) to only store the ipv6 since that is actually ur own and u will be able to connect through ipv6 even if ur ISP is using CGNAT
Just stick the ipv6 into you wireguard setup.
Yes CGNAT the way for cheap ISPs.
Statistics: Posted by Kartohfel — Sun Dec 28, 2025 2:49 pm