Fix DNS Server Failure 0x232A in 3 Steps

You're staring at that error: DNS_ERROR_RCODE_SERVER_FAILURE (0X0000232A). It's Windows telling you the DNS server it talked to basically threw its hands up and said, "I don't know, and I'm not going to try." Not a timeout—an outright refusal. This usually happens when the DNS server is overloaded, misconfigured, or blocking your request for some reason.

I've seen this pop up on Windows 10 and 11, often when you're on a flaky home network or a strict corporate one. The fix is usually straightforward, but you need to go in order. Don't jump to the advanced stuff—try the cheap fixes first.

Fix 1: The 30-Second Try — Flush Your DNS Cache

Sometimes your PC holds onto a bad DNS result. It's like asking for directions, getting them wrong, and then refusing to ask again. Flushing clears that memory.

Press Windows key + R, type cmd, and press Ctrl+Shift+Enter to open Command Prompt as administrator. Click Yes if prompted.
Type this and hit Enter:
```
ipconfig /flushdns
```
You should see Successfully flushed the DNS Resolver Cache. If you get an error instead, you didn't run as admin. Close and reopen the prompt with those keys.

After that, try the website again. If it loads, done. But honestly, this only fixes it about 10% of the time. The cache usually isn't the culprit for a server failure code.

Fix 2: The 5-Minute Fix — Restart Your Router and Check Its DNS

Your router is the middleman. It hands your PC a DNS server address, usually from your ISP. If that ISP server is having a bad day, you get this error. Restarting the router forces it to re-establish its connection and often picks up a fresh DNS lease.

Unplug your router's power cord. Wait a full 30 seconds—no shortcuts.
Plug it back in. Watch the lights. Usually, the internet light goes solid after a minute or two.
On your PC, restart your network adapter: open Settings → Network & Internet → Advanced network settings → More network adapter options. Right-click your active adapter (Wi-Fi or Ethernet) and select Disable, then wait 5 seconds and Enable it.

If that doesn't work, log into your router (usually at 192.168.1.1 or 192.168.0.1) and see what DNS servers it's using. Look for a section called Internet, WAN, or DNS. If it's set to Obtain automatically from ISP, try switching to Use the following DNS server addresses and put in these public ones:

Primary: 8.8.8.8
Secondary: 8.8.4.4

Save the change. That's Google's DNS—it's fast and rarely down. Your router will reboot itself. After it comes back up, try your site again. This fixes the issue for most people I've helped.

Fix 3: The 15-Minute Fix — Change Windows DNS Settings Directly

If your router is fine but the error persists, the problem is on your PC. Windows might be using a specific DNS server that's failing. Let's override it per adapter. This is more reliable than router settings because it works even if your router has weird settings.

Open Control Panel → Network and Sharing Center → Change adapter settings.
Right-click your active connection and choose Properties. If you're on Wi-Fi, that's your Wi-Fi adapter; if Ethernet, the Ethernet one.
Find Internet Protocol Version 4 (TCP/IPv4) in the list. Highlight it and click Properties.
Select Use the following DNS server addresses. Enter:
```
Preferred: 1.1.1.1
Alternate: 9.9.9.9
```
Make sure Validate settings upon exit is checked, then click OK. Windows will run a quick test—if it passes, great.

Why these? 1.1.1.1 is Cloudflare's DNS—it's known for speed and privacy. 9.9.9.9 is Quad9, which blocks malicious sites. They're both solid choices. Google's 8.8.8.8 works too, but I prefer these for the extra security layer.

Now, open Command Prompt again and run:

ipconfig /flushdns
nslookup example.com

The second command should return an IP address, not an error. If you see server failure again, then the problem isn't your DNS settings—it's something upstream, like your ISP blocking you. Try a different network (like your phone's hotspot) to confirm.

A real-world trigger: You're at a coffee shop using their free Wi-Fi. Their router is overloaded and its DNS is failing. The router restart won't help because you don't have access. Change your Windows DNS settings to 1.1.1.1, and you're back online in two minutes.

One last thing—make sure your system time and date are correct. A wrong time can cause SSL errors, but it also messes with DNS in rare cases. Right-click the clock → Adjust date/time → Toggle on Set time automatically.

If none of these steps get you online, the issue is likely on the server side. Wait an hour and try again. DNS failures usually resolve themselves because the servers recover. But you've covered all your bases for the local part.