Advertisement

Windows DNS Client Works on One Port but Not Another

If Windows DNS works on one port but not another, the Windows DNS Client service is usually not the problem. This article shows how to tell whether the failure is name resolution, the server listener, a firewall rule, or an app using a different protocol.

Networking 7 min read
Windows laptop

If Windows DNS works on one port but not another, the Windows DNS Client service is usually not the fault. Most of the time, the mismatch is in the protocol, listener, firewall, or the path an app is using. Start by checking whether the failure is name resolution, the DNS server listener, or a port the app probes separately.

Symptom

What you usually see is one of these patterns: name resolution works in one tool but not another, UDP queries get answers while TCP does not, or a port check says the service is unreachable even though normal browsing still works.

That often means the problem is not “DNS” in the broad sense. A browser can look fine because it may use cached answers, DoH, or a different resolver path. Your test may be hitting a specific port or transport that is blocked or not listening.

Before you start

The Windows DNS Client service sends lookup requests and caches the answers it gets back. It does not make every port usable. Standard DNS lookups normally use UDP 53 and sometimes TCP 53, so a difference between ports usually points to protocol behavior or a server/listener problem, not the client service itself.

Before you change anything, decide what you are actually testing:

  • Name resolution: can Windows turn a name into an IP address?
  • DNS reachability: can the target DNS server answer on the expected port and transport?
  • Application reachability: can the service behind a custom port be reached at all?

Also check the Windows features that can silently change the path a query takes:

  • Custom DNS servers assigned on the adapter
  • DoH in the browser, app, or system path
  • NRPT rules in managed or VPN-connected environments
  • VPN clients that push their own DNS servers or routes

If you are working on a managed device, be cautious with policy-based settings. If a VPN or NRPT rule is in play, the machine may not be using the DNS server you think it is.

How to tell where the failure is

Use a simple decision flow and don’t mix the tests together.

What happensLikely problemWhat to check next
nslookup failsClient path, DNS server, or policyDNS server address, VPN, NRPT, adapter settings
nslookup works but the port test failsListener or firewallServer listener, firewall rule, transport mismatch
UDP works but TCP does notTCP listener or TCP blockedServer service, firewall, appliance rules
Browser works but nslookup failsDifferent resolver pathDoH, cache, VPN, NRPT
A custom service port failsNot a standard DNS issueApplication listener and app-specific firewall rule

A clean mental model helps here. The client asks for a name, the DNS server answers, and a separate service may listen on some other port. If one protocol works and the other does not, that can be normal when the server is only meant to answer on one transport. It can also mean the firewall or listener is incomplete. Standard DNS on Windows is about port 53. A custom port needs separate confirmation from the application or server documentation.

How to test from Windows without guessing

Start with name resolution, then test port reachability separately. nslookup tells you whether the configured DNS server answers the query at all. Test-NetConnection tells you whether the network path reaches a specific port.

PowerShell (run as Administrator)
nslookup example.com
Test-NetConnection your.dns.server -Port 53

If nslookup fails, focus on the DNS path: adapter settings, VPN, NRPT, the server address, or the server itself. If nslookup works but the port test fails, you are usually looking at a listener or firewall issue, not name resolution.

If you want to compare protocols, test the same target from the same Windows machine and keep the destination constant. If UDP answers but TCP does not, that points to a protocol-specific problem on the server or along the path. If the server answers on 53 but the application still fails on a different port, stop treating it like DNS. Check the app’s listener and firewall rule instead.

Safe fix order

  1. Confirm the port and protocol you expect.
Reference
Standard DNS: UDP 53 and TCP 53
Custom service port: application-specific, not a Windows default
  1. Check whether Windows can resolve a name.
PowerShell (run as Administrator)
nslookup yourname.example.com

If this fails, fix the DNS server address, VPN path, or NRPT rule before you touch ports. That keeps you from breaking a working listener while the real problem is actually the resolver path.

  1. Test the target port separately.
PowerShell (run as Administrator)
Test-NetConnection your.dns.server -Port 53

If the port test fails but name resolution works, the listener or firewall path is the likely issue. If TCP fails and UDP works, that may be normal for the service you’re testing. That is only true when the service is designed to allow one transport and not the other.

  1. Check the Windows settings that can redirect DNS.
Settings path
Settings > Network & internet > Wi-Fi or Ethernet > Hardware properties > DNS server assignment

Then review any DoH settings, VPN policy, and NRPT rules in the environment. If traffic is being sent to a different server than you expected, the working and failing tests may not be hitting the same destination.

  1. Change only the side that is actually broken.

If the DNS server answers on UDP but not TCP, fix the TCP listener or firewall rule. If a custom port fails, fix the application or its listener. If nothing resolves, correct the server address or DNS policy first, then retest before making deeper changes.

Verify the fix

Run the same tests from the same Windows machine that showed the problem.

You want both of these to line up: the name resolves from the DNS server you intended, and the port you expect responds on the protocol you expect. If one protocol still fails while the other works, that is only acceptable when it matches the design of the server or application.

If the browser works, nslookup works, and the custom port still fails, stop calling it a DNS issue. At that point, the likely problem is the application listener, its firewall rule, or the service configuration.

Conclusion

If the behavior is still split between ports after these checks, stay on the side that’s failing and test that listener or policy path next. Don’t keep changing DNS settings once name resolution is already working.

Frequently Asked Questions

What does the Windows DNS Client service actually do?

It sends lookup requests and caches answers for Windows. It does not make a server listen on a port or force a firewall to pass traffic. If one port works and another does not, the DNS Client service is usually only part of the path.

Why do DNS lookups normally use port 53?

Standard DNS uses UDP 53 and sometimes TCP 53. If another port is involved, that is usually an application-specific setup, so you should verify the server and the app separately.

Could VPN or DoH change the result?

Yes. VPN policies, DoH, and NRPT rules can send DNS traffic somewhere other than the path you expected. That can make one test succeed and another fail even when the local Windows DNS settings look fine.