Yeah, I have my own DNS server that caches from multiple backing servers as needed. I'm not worried about DNS blocking, it's never been effective. The issue is ISP level blocking usually isnt just DNS blocking, it's also involves IP level blocking, many of which dont work on IPv6 which is one reason (besides just resistance to replacing old hardware) it hasn't been adopted widely by consumer ISPs. If you have only a single, unchangeable (by anyone other than them) IP address, they have much more control and your traffic is much easier to track and manipulate.

And there is even lower level blocking at lower layers of the network stack. ISPs can intercept and mangle packet's destinations at any layer because your traffic must go through them and so your networking equipment must trust their equipment to properly route traffic. They don't do it now mostly because it means adding a lot more processing power to analyze every packet. I do it all the time at home to block ads and other malicious traffic. But if they're required to upgrade to allow for that level of traffic analysis, by law, then that opens the floodgates for all kinds of manipulation either politically or capitalistically nefarious in nature.

Best solution is not using dns in the first place though.

Use DNS over HTTPS (or TLS or QUIC). I think some browsers use it by default now. If there's country-specific blocks, use your own recursive DNS server, or one in another country.