It's likely not a misconfiguration, but it's a bad practice [1] to implement dynamic IPv6 prefixes like they were IPv4 addresses from a pool. I see no reason to do it like this other than "that's what we have always done with IPv4".
Non-sticky, dynamic prefixes cause all sort of mayhem because suddenly your RAs, firewall rules, DNS recods, NAT64 pools etc. are all outdated and you have to somehow update them, leaving the network in a broken state until the changes have propagated.
They probably do it so you have to pay for a static one.
Yeah it’s annoying enough that I had to set up my DNS server on a ULA network, so I can hardcode it in my RA without thinking about ISP prefixes. As for NAT64, I just stuck to the well-known 64:ff9b instead of using my own prefixes. It also simplifies DNS64.
I hear that this is a common practice nowadays across worlds' ISPs though :/
> It's likely not a misconfiguration, but it's a bad practice [1] to implement dynamic IPv6 prefixes like they were IPv4 addresses from a pool.
I don't necessarily disagree with the assessment, but to a certain extent I like getting new addresses/prefixes to help with privacy: with my previous ISP I had my own Asus router (now have to use ISP-provided), and it had built-in functionality to schedule reboots.
* https://www.asus.com/support/faq/1049258/
I would get a new IPv4 address and IPv6 prefix each day.
Yes, there are (e.g.) browser-based mechanisms for tracking, but if I open sites in (say) a private window I would avoid some of those; there are also add-ons/extensions that allow for (auto-)expiring cookies.