DNS name not found (0x0000232B) – quick fix that works

30-Second Fix: Check the name yourself

Most of the time, this error means you typed something wrong. I've lost count of how many times a client swore the hostname was correct, and I found a missing letter.

1. Open Command Prompt as admin (right-click Start > Command Prompt (Admin)).
2. Type nslookup the-hostname-you-typed – replace with the actual name.
3. Look at the output. If you see "*** UnKnown can't find ...: Non-existent domain", the DNS server has no record for it.

If the name is wrong, fix the typo in whatever app or script is trying to use it. Happens all the time with internal server names – someone mis-copied a SharePoint URL or a database alias.

5-Minute Fix: Flush DNS and check the cache

Sometimes the DNS record exists but your machine is holding a bad cached response. This is common after a failover or when a server's IP changed but the old record stuck around.

ipconfig /flushdns
ipconfig /registerdns
netsh int ip reset

After running those, try the lookup again. If it works, you're done. This fixes maybe 30% of cases I see – clients who've been using the same stale DNS for hours.

While you're at it, check your DNS server settings. Open Control Panel > Network and Sharing Center > Change adapter settings. Right-click your active network adapter, go to Properties, double-click Internet Protocol Version 4 (TCP/IPv4). Make sure Obtain DNS server address automatically is set, or if you use manual DNS, that the servers are reachable. Had a client last month whose IT guy set a dead internal DNS server as primary – nslookup worked on the secondary but failed on the primary.

15+ Minute Fix: Investigate the DNS server itself

If the name is correct and flushing didn't help, the issue is on the DNS server. This is where you need admin access to the DNS server.

1. On the DNS server, open DNS Manager (dnsmgmt.msc).
2. Expand the server name, then Forward Lookup Zones. Find the zone that should hold the record.
3. Look for the hostname. If it's missing, you need to add it. Right-click the zone, choose New Host (A or AAAA), enter the name and IP.
4. If the record exists but is expired or grayed out, it's probably a stale record from a scavenging event. Delete it and re-add, or force a replication if you're in a multi-DNS environment.

Another common culprit: the DNS server itself can't resolve the name because its upstream forwarders are broken. Run dcdiag /test:dns on a domain controller to check DNS health. I've seen cases where a forwarder pointed to a retired ISP DNS server – changed it to 8.8.8.8 and everything worked.

When to skip all this

If you're trying to reach an external website and you get this error, it's probably not your DNS – it's the website's. Check with nslookup google.com – if that works, the problem is specific to the domain you're trying to reach. Wait a bit, it might be a temporary outage.

If you're on a corporate network and see this error for internal resources, call your network admin. They'll need to check the DNS zone delegation or the server's static entry.

Bottom line: 0x0000232B is almost always a missing record or a bad name. Flush your cache first, check your typing second, then dig into the DNS server. Don't waste time reinstalling network drivers – that's never the fix.