Resolve-DnsName works against one DNS server only

Incident 2 min read Troubleshooting walkthrough

Work the problem

Two resolvers disagree

Fictional case: One resolver returns the expected A record. Another returns NXDOMAIN for the same name and type.

What is the next useful comparison?

Reasoning notebook

Record the evidence that supports your answer and the check you would run next. Your notes stay in this browser — nothing is uploaded.

Your hypothesis and reasoning

Why it happens

The DNS servers do not currently hold equivalent data. Common causes are replication lag, a missing zone, stale conditional forwarding, split-brain design or cache differences.

Check this first

1PS> $DnsServer = '10.20.30.10'

2PS> Get-DnsClientServerAddress -AddressFamily IPv4

3PS> Resolve-DnsName -Name app.example.test -Server $DnsServer -Type A -DnsOnly

What to look for

NXDOMAIN is a DNS response. Compare authoritative data and resolution paths before clearing caches indiscriminately.

Working through it

Query each configured resolver directly with the same name and record type.
Identify whether the failure is NXDOMAIN, timeout or a different answer; those point to different layers.
On authoritative servers, compare zone presence, record data and replication state before clearing caches.
Correct the authoritative or forwarding configuration, then repeat the direct queries.

Avoiding it next time

Verify the repair: Query both resolvers directly with the same name and type after correcting the responsible DNS configuration.

Primary documentation

PowerShell objects and pipelines documentation