Windows 10: DNS cache issues on windows 11

I have an acer nitro . I installed the KB5054979 cumulative update for. . Net framework 3.5 and 4.8.1 for windows 11 version 24H2 and my dns cache started having problems . I flushed it and nothing. I did a network reset and nothing . I was gonna factory reset when I decided to try uninstalling the update and that seemed to fix it? But why did it break?

:)

 

DNS server causing problem

Hi Andrea,

DNS is a server that translates websites' addresses so that browsers can connect to them. If the addresses become outdated or the server has issues, problems and DNS errors occur. For us to provide an accurate solution, we would need you to answer the following
questions:

• Which build, version and edition of Windows is installed on your computer?
• What changes have you made to your device before this issue occurred?
• Are you experiencing the same issue regardless if you are trying to be connected to a wired or wireless connection?

For initial troubleshooting, we suggest deleting the DNS cache. This can refresh the DNS files and settings on your PC. Follow these steps to delete the DNS cache:

• Using Search type Command Prompt.
• Form the search results, right click on Command Prompt (Desktop app) and then choose Run as administrator.
• In the Command Prompt window, type ipconfig /flushdns and then hit the Enter key.
• Once done, restart your computer and then check if the same issue persists.

We are looking forward to your response.

 

Windows 10 DNS caching problem

After some time of messing around with the two windows 10 machines I have, one a laptop, the other a surface pro 4, I've consistently hit the DNS resolution issues that many other people have reported.

Basically what happens is DNS resolution stops functioning for a period of time, however previously cached domains still resolve. A simple and effective solution to this is to just flush dns cache with ipconfig /flushdns command. More frustrating is that
it appears when DNS resolution fails, nxdomain is cached as well (which may actually be a significant part of the problem).

Microsoft network engineering should take a good look at how the resolver cache is handled, as it appears that some failure which results in DNS resolution failure will end up with a cached nxdomain (which should never happen). The fact that a simple dns
flush fixes the problem instantly strongly suggests that there is a bug in this part of the code which needs closer examination.

 

DNS SERVER NOT RESONDING

Hi Rita French,

This issue often occurs when the DNS settings are incorrect. I suggest you to perform the following methods to troubleshoot the issue.

Method 1:

I would recommend you to change the Preferred DNS server and check if it helps.

• Press Windows + R keys to open Run window, type
  ncpa.cpl and press Enter.
• Right-click on the connection that you use for the local connection, and then click
  Properties.
• Click to select Internet Protocol Version 4 (TCP/IPv4), and then click
  Properties.
• In the Internet Protocol window, let's change the Preferred DNS server to
  208.67.222.222
• Click OK twice to complete the modification.

Note: If the issue persists, please repeat the steps and change the "Preferred DNS server" to 208.67.220.220.

Method 2:

If that does not help, try to flush the DNS. Follow these steps below.

• From Start screen, type Command Prompt.
• Right-click on Command Prompt and choose Run as Administrator.
• Type: ipconfig /flushdns and press Enter.

Note: The ipconfig /flushdns command provides you with a means to flush and reset the contents of the DNS client resolver cache. During DNS troubleshooting, if necessary, you can use this procedure to discard negative cache entries from the cache, as well
as, any other dynamically added entries.

Hope any of these methods help!

Kind regards,

Leon