Three solutions to Fix “Outdated Entry in the DNS Cache” Problem

DNS cache error

“We recently installed some new Windows servers but are unable to Remote Desktop into them from our Windows 10 PCs. The remote desktop connection is established, but we receive an error message shown in the image after providing credentials. These are the correct IP addresses. Do you have any advice?”

How to fix “outdated entry in the DNS cache” problem

How to fix outdated entry in DNS cache? Here in this post, we summarize three tested ways to help you troubleshoot “outdated entry in the DNS cache” Remote Desktop problem.

Solution 1. Reset the local DNS cache

In most cases, the server IP address had changed, and the DNS on the DC was still holding the old value. The fix was to run ipconfig /registerdns on the problem server and run ipconfig /flushdns on the client.

Step 1. Press Win + R, and then type in “cmd” to open Command Prompt.

Step 2. Just in case, type in the following command to run the server record registration in DNS again:

ipconfig /registerdns

Step 3. Then type in the following command to reset the local DNS cache on the client in a couple of minutes:

ipconfig /flushdns

Solution 2. Check the time difference between the DC and client

If no changes to the DNS or computer names have been made, the problem is almost always due to time synchronization. Check that the server's clock is properly synchronized and that the client computer's time is within 5 minutes of the correct time.

Step 1. On the remote host, search for Command Prompt in the Search box, and then click Run as administrator. 

Step 2. Type in the following commands and press Enter:

net stop w32time

net start w32time

Now logoff from the server and RDP the server using host name. You will be able to login.

Solution 3. Change the Remote Desktop security to RDP security layer

This may also be caused by the RDP security layer. This error message typically indicates that network congestion is preventing a secure connection to the server. When the server is using the TLS security layer for secure connections and TLS is not supported on the client computer, this error message may appear.

 Step 1. Press Win + R, then type in “gpedit.msc” and press OK to open the Local Group Policy Editor window.

Step 2. Navigate here: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.

Step 3. Find and click Require use of specific security layer for remote connections, then change its status to Enabled. Choose the security layer (Negotiate, RDP, SSL) from the drop-down list.

AnyViewer: remote desktop software without restriction

If you’re looking for easy remote desktop software that allows you to achieve remote control as long as two computers are connected to the Internet, you can use AnyViewer. With its intuitive interface and concise operating steps, users can easily get started with AnyViewer.

Step 1. Download, install and launch AnyViewer on both computers. Go to Log in, and then click Sign up. (If you already have signed up on its official website, you can log in directly.)

Step 2. Fill in the signup information.

Step 3. Then you can see you successfully logged in to AnyViewer. Your device will automatically be assigned to the account you've logged in.

Step 4. Log in to the same AnyViewer account on the two devices, then you can achieve a direct connection by clicking One-click control.

Conclusion

This post mainly introduces how to fix “outdated entry in the DNS cache” problem. Specifically, three solutions are introduced. The first is to reset the local DNS cache, the second is to check the time difference between the DC and client, and the third is to change the Remote Desktop security to RDP security layer. Besides, if you’re looking for easy remote desktop software, AnyViewer is recommended to you to help you start remote control easily.