How to Fix Windows can’t resolve domain name

It has come to our attention that there are times when Windows cannot resolve domain names in the case of running nslookup or pinging. This is sometimes occasional; they try using nslookup, and it works, but then again, pinging the same hostname doesn't. In this post, we review the problem and determine how to fix it when Windows is not resolving domain names. This piece is going to cover the matter in WSL, too.

My domain won't resolve. What's the deal?

Fix Windows can’t resolve domain name

Incorrect DNS can cause your system to fail in resolving a domain. This becomes resolved if the record in the Cloudflare DNS leads to some non-resolvable external domain. Otherwise, the record points to a valid origin IP address. I would recommend that you start with ensuring that all the documents are done and up-to-date. If that's not the case, then the following things are what I'd try:.

Helps Windows resolve domain name conflicts

First things first: try restarting the server if, after all this, Windows is unable to resolve the domain; could be a bug. If that doesn't work or isn't an option since it's in production, try the options below.

Try manually registering DNS

Check IP configuration

Let outgoing DNS queries pass through server firewall

Repair GPO Broken Files

Rebuilding Protocols for the Networks

Now, let's look into their details.

1. Try to configure DNS manually.

Due to activity or patching, the backend may unregister and then reregister a device at some time. At this point, the customer might have to manually enter registration information of the device into his computer. Open the Command Prompt as administrator and create below command to do so.

"ipconfig /registerdns"

Finally, try rebooting your computer and see if it works.

2. Check Your IP Settings

Make sure your NetBIOS Setting is matching your DNS setting and check your computer's IPv4 configuration, too. Follow the steps described below to do so.

Open Server Manager.

To open the Local Server, under Ethernet, WiFi (if that's the case), click the hyperlink that will be appearing alongside it.

Right-click your network to enter into its properties.

Click on Properties again.

In the properties list, scroll down and click on Internet Protocol Version 4 (TCP/IPv4).

Once you click on Advanced click on the Wins tab.

By default, the box is checked in the NetBIOS configuration to use the configuration provided by the DHCP server. You can enable it manually using TCP/IP to ensure everything works correctly with a static IP address and/or when the DHCP server doesn't have an option to configure NetBIOS. Click the "Enable NetBIOS over TCP/IP" button.

Click the "Ok" button.

Finally, verify that the problem is fixed.

3. Open the Firewall on the Server to allow DNS requests to go out.

Now, the next thing to be done with the firewall is allowing the outgoing requests for DNS. This should be done by the administrative personnel on the server or the one who has access to the Server Manager. This can be done simply by following the steps mentioned below.

Run Server Manager.

Open Tools menu and click on Windows Defender Firewall with Advanced Security.

From the left side of the Window, click on Outbound Rules and then New Rule.

In Rule Type section, click Port followed by Next.

Protocol and Ports: Click UDP and, in the field provided below, type port 53.

Click.

Under the tab Action, select Allow the connection and click Next.

Then choose for what type of profile you want this rule to apply to and click the button Next.

You can name the rule as you like, such as "Outgoing DNS Requests," then click Finish.

Next, you will be able to see the rule listed under Outbound Rules and verify that it's enabled.

4. Repair Damaged Local GPO Files

You can have this problem if there are corrupted local GPO files. This is the reason Windows cannot apply the DNS policy and is outputting the above error. We are going to delete the files and will try to apply the GPO changes to sort out the issue. Follow the same by following the steps provided below.

Before anything else, start File Explorer on the client machine and rename or delete C:WindowsSystem32GroupPolicyMachineRegistry.pol.

Login as an administrator to get started, then launch Command Prompt.

Run the command gpupdate/force.

What this does is reapplies the Group Policy taken by the server administrator. Go ahead and check to see whether or not the issue has been resolved.

Note: GPUpdate Force does not work for Windows PCs.

5. Network Protocol Reset

Do a network protocol reset on the client, just in case the problem still occurs after you have manually updated the GPO. To do this, open Command Prompt as an administrator and run the following commands.

Disable TCP/IP

ip reset-input-str

Restart Windows

Reset winsock using netsh

Renew DNS

ipconfig /flushdns launched DNS configuration "ipconfig /registerdns"

Lastly, verify that the problem is fixed.

The following steps will hopefully help find the cause and perhaps repair the "Windows can't resolve domain name" error.