Hi there,
It looks like the behavior you’re experiencing with the DNS Client service (DNSCache) repopulating on resume from hibernation is now occurring after the 24H2 update and isn’t something that can be directly controlled through any Group Policy or registry setting.
In previous builds the DNS cache was refreshed only on a cold boot, and this change appears to be an intentional modification by Microsoft.
One potential workaround would be to set up a scheduled task that stops the DNS Client service upon resume, though this isn’t recommended because disabling DNS caching can negatively affect name resolution and overall system performance.
The best approach at this time is to provide feedback via the Windows Feedback Hub so Microsoft can review whether this change is impacting users significantly and consider a fix in a future update.