Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x0000232B

DNS error 0x0000232B: the client cannot resolve internal or external names

11 min read Updated October 5, 2026 Networking, Sharing & Printing

Fix it now

0x0000232B is DNS_ERROR_RCODE_NAME_ERROR, which Microsoft states simply as “DNS name does not exist”. A server answered and said no. That is different from a timeout, and it is useful: the query reached a resolver and came back. Either the record genuinely is not there, or you asked a server that has no business knowing about it.

Run these in an elevated PowerShell, substituting your own name and internal server

ipconfig /all
Get-DnsClientServerAddress
Clear-DnsClientCache
Resolve-DnsName server.example.local -Server 10.0.0.10
  1. Read the DNS servers on the adapter that actually carries your traffic, not the first one listed. A public resolver in that list is the single most common cause of a confident wrong answer about an internal name.
  2. Ask your internal server directly with Resolve-DnsName <name> -Server <internal ip>. If it answers and the client does not, the client is asking somewhere else.
  3. Correct the list where it is wrong: Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 10.0.0.10,10.0.0.11. If the addresses come from DHCP, fix the scope option instead of the client.
  4. For short names, check the suffix search order with Get-DnsClientGlobalSetting and confirm your internal domain suffix is in it.

Check C:\Windows\System32\drivers\etc\hosts before you go further. A stale entry there overrides every resolver on the machine and produces failures that survive any amount of DNS work.

If the name resolves and keeps resolving after a reboot, you are done. If not, the next section covers the other answers a resolver can give and what each one means.

Why it happens

A DNS response carries a result code, and Windows surfaces those codes directly. A name error – 0x0000232B – means the server that answered told the client that no such name exists. The client believes it and caches that answer, which is why a fault can outlive the fix by minutes: the record was created, and this machine is still repeating the last confident no it was given.

The most common way to get a confident wrong answer is to ask the wrong server. A public resolver knows nothing about your internal domain and will correctly report that your file server does not exist. Mixing an internal server and a public one on the same adapter is the classic version: queries go to whichever answers, so internal names resolve intermittently and fail without a pattern anyone can see. Domain-joined clients should point only at internal DNS servers, and those servers should forward what they cannot answer.

The neighbouring codes describe the other answers. 0x0000232A is DNS_ERROR_RCODE_SERVER_FAILURE – Microsoft’s text is “DNS server failure” – meaning the resolver tried and could not complete the query, which usually points at a forwarder or at validation rather than at the record. 0x0000232D is DNS_ERROR_RCODE_REFUSED, “DNS operation refused”: the server could answer and has been configured not to for you. 0x00002329 is DNS_ERROR_RCODE_FORMAT_ERROR, “DNS server unable to interpret format”. And 0x0000267C is different in kind and worth ruling out first: DNS_ERROR_NO_DNS_SERVERS, no DNS servers configured for the local system at all.

The client is asking a public resolver about an internal name

You have this one if Public websites work, internal names fail, and ipconfig /all lists a public resolver alongside or instead of your own servers.

  1. Point the adapter at your internal servers only: Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 10.0.0.10,10.0.0.11.
  2. Configure forwarders on those internal servers so external names still resolve.
  3. Where the addresses come from DHCP, correct the scope option rather than each client, then ipconfig /renew.
  4. Clear the cache and retest with Resolve-DnsName.

A public resolver as a secondary entry is not a safety net. Windows may use it for any query, so internal names fail unpredictably rather than never – which is much harder to diagnose.

A short name with no matching suffix

You have this one if server fails and server.example.local succeeds.

  1. Read the current search order: Get-DnsClientGlobalSetting.
  2. Set what you need: Set-DnsClientGlobalSetting -SuffixSearchList @("example.local","branch.example.local").
  3. On domain members, confirm the primary DNS suffix is right in System properties under Computer Name, Change, More.
  4. Prefer fully qualified names in scripts and configuration files so they do not depend on the search order at all.

A cached negative answer

You have this one if The record has been created or corrected, other machines resolve it, and this one still insists it does not exist.

  1. Look at what is held: Get-DnsClientCache | Where-Object Entry -like "*name*".
  2. Clear it: Clear-DnsClientCache.
  3. Retest immediately. If it fails again straight away, the record really is missing on the server and you are in the next cause.

The record was never created, or scavenging removed it

You have this one if Every client fails on the same name, and the record is absent when you look in the zone.

  1. On the machine that should own the name, re-register with Register-DnsClient, then check the zone again.
  2. For a device that cannot register itself – a printer, an appliance – create a static record.
  3. Check whether ageing and scavenging removed a record nothing was refreshing, and either exclude it or make it static.
  4. Where dynamic updates are secured, confirm the client has permission to update its own record.

A VPN, encrypted DNS or adapter order is sending queries elsewhere

You have this one if Resolution changes depending on whether a tunnel is up, or the adapter you have been configuring is not the one carrying traffic.

  1. List every adapter’s servers with Get-DnsClientServerAddress and identify which adapter is actually in use.
  2. Check for DNS over HTTPS on the adapter: Get-DnsClientDohServerAddress shows which resolvers are configured for encrypted DNS.
  3. Check the Name Resolution Policy Table with Get-DnsClientNrptPolicy, which is how VPN clients commonly redirect specific namespaces.
  4. Compare interface metrics with Get-NetIPInterface where two adapters are both up and competing.

Full reference

Every code in this family, as Microsoft publishes it

Code Constant Microsoft’s text
0x0000232B DNS_ERROR_RCODE_NAME_ERROR DNS name does not exist
0x0000232A DNS_ERROR_RCODE_SERVER_FAILURE DNS server failure
0x0000232D DNS_ERROR_RCODE_REFUSED DNS operation refused
0x00002329 DNS_ERROR_RCODE_FORMAT_ERROR DNS server unable to interpret format
0x0000267C DNS_ERROR_NO_DNS_SERVERS No DNS servers configured for local system

Reading them as a set saves time. A name error is an answer, so the query path works and you are arguing about content. A server failure or a refusal means the path works and the server declined, so the fault is on the server or in its forwarding. No DNS servers configured is not a resolution failure at all – it means the client has nowhere to ask, which is a DHCP or adapter problem wearing a DNS costume.

Command reference

Command What it does
ipconfig /all Shows the configured DNS servers and the connection-specific suffix per adapter
Resolve-DnsName <name> -Server <ip> Queries one named server, bypassing the configured list entirely
Clear-DnsClientCache Empties the resolver cache, including cached negative answers
Get-DnsClientCache Shows what the resolver is currently holding, and for how long
Get-DnsClientServerAddress Lists the servers set on every interface, which is where surprises live
Get-DnsClientGlobalSetting Shows the suffix search list used for short names
Register-DnsClient Asks the client to register its own records with the DNS server
Get-DnsClientNrptPolicy Shows namespace-specific resolution rules, the usual VPN mechanism

Encrypted DNS and the internal namespace

Windows can be configured to send queries over DNS over HTTPS, and the DnsClient module exposes that directly through Get-DnsClientDohServerAddress, Add-DnsClientDohServerAddress and Set-DnsClientDohServerAddress. Encryption is not the problem; destination is. A client that resolves through a public encrypted resolver will get an authoritative-sounding name error for every internal name it asks about. On a domain, encrypted DNS belongs pointed at resolvers that know your zones, or it belongs off for the adapters that must use internal servers.

When the answer keeps changing

  • Test the same name from two clients on the same subnet. Two different answers means the clients are using different servers, not that the record is flapping.
  • Test with -Server against each internal DNS server in turn. One server missing a record is a replication or zone-transfer problem rather than a client one.
  • Watch for split-brain DNS, where an internal zone and an external zone share a name and hold different records. The client that resolves “correctly” may be the one giving you the wrong address.
  • Check the hosts file on any machine that behaves uniquely. It is checked before the resolver and it survives every cache flush.
  • On a machine with several active adapters, remember that the resolver sends the query out of the interface with the lowest metric first.

Negative caching, and where it is configured

The DNS Client service caches failures as well as successes, which is deliberate and stops every application on the machine hammering a server for a name that does not exist. The lifetime is a property of the DNS Client service and is configurable through that service’s own parameters, but it is rarely the right thing to change: a shorter negative cache masks the underlying problem and increases query load across the estate. Clear-DnsClientCache gives you the same effect for one machine at the moment you need it, without leaving a setting behind for someone to find in two years.

Changing DNS Client service parameters affects every lookup the machine makes, including the ones that locate domain controllers. Export the service key before editing it, change one value at a time, and restart the DNS Client service so the change takes effect.

Every code this article covers

Code What it points at Source
0x0000232B DNS_ERROR_RCODE_NAME_ERROR: DNS name does not exist – a server answered and said the name is not there Microsoft Learn
0x0000232A DNS_ERROR_RCODE_SERVER_FAILURE: DNS server failure, so the resolver could not complete the query Microsoft Learn
0x0000232D DNS_ERROR_RCODE_REFUSED: the DNS operation was refused for this client Microsoft Learn
0x00002329 DNS_ERROR_RCODE_FORMAT_ERROR: the DNS server was unable to interpret the format of the query Microsoft Learn
0x0000267C DNS_ERROR_NO_DNS_SERVERS: no DNS servers are configured for the local system, so there is nothing to ask Microsoft Learn

Confirm the fix worked

  1. Resolve-DnsName <name> returns the address you expect, without a -Server override.
  2. ipconfig /all shows only the intended DNS servers on the adapter carrying traffic.
  3. A short name and a fully qualified name both resolve, which tells you the suffix search order is doing its job.
  4. Get-DnsClientNrptPolicy and Get-DnsClientDohServerAddress return nothing unexpected for the namespace you care about.
  5. Reboot, then resolve the same name again, so you know the configuration is persistent rather than a temporary override.

Questions people ask about this

Does this cost anything to fix?

No. Every command and setting here is part of Windows, and correcting a server list or creating a missing record costs nothing but the time to do it.

Should I just use a public resolver everywhere?

Not on a domain. Domain members need internal DNS to find domain controllers and internal services. Point clients at your internal servers and let those forward external queries onwards.

Why does it work on my phone and not my laptop?

Usually because the phone is only resolving public names. Test the same internal name from both, and check which DNS servers each device was given.

How long will a wrong answer stay cached?

Until the entry’s lifetime expires or you clear it, which is why Clear-DnsClientCache belongs in your first few steps rather than at the end. Negative answers are cached like any other.

The error is 0x0000267C rather than 0x0000232B. Is that the same problem?

No, and it is the easier one. That code is DNS_ERROR_NO_DNS_SERVERS: the machine has no DNS servers configured at all, so nothing was asked. Look at DHCP, at the adapter configuration and at whether the right adapter is up, not at the zone.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error Error 0x80092012: TLS inspection breaks certificate checks on the client License Error RDP error 0x80090326: the TLS handshake was rejected before logon Free Fix Remote Desktop cannot verify the identity: certificate error 0x80090325 Free Fix 0x80070005 access denied on a network share you are sure you can open
โ† Back to Knowledge Base