• Donate
    TheWindowsForum.com needs donations to stay online!
    Love TheWindowsForum.com? Then help keep it alive by sending a donation!

Windows 11 Repair DNS Server Failure 0x8007232A: 3 Methods to Fix It

WELCOME TO THEWINDOWSFORUM COMMUNITY!

Our community has more than 63,000 registered members, and we'd love to have you as a member. Join us and take part in our unbiased discussions among people of all different backgrounds about Windows OS, Software, Hardware and more.

AFFASocial

Ultimate Donator
VIP
Jun 26, 2021
759
496

  • DNS server failure 0x8007232A is a Windows error indicating the computer cannot resolve the name of a Key Management Service server.
  • The inbuilt Windows Network troubleshooter will be the most practical solution for most users encountering this error.
Windows-11-dns.png




If you encounter the error code 0x8007232A, you face a DNS Server Failure. This Windows error code indicates your computer cannot resolve the name of a Key Management Service server. It will not be able to find the server’s IP address and will not activate Windows.

We will show you how to fix it in this guide. You may read our other guide to learn troubleshooting steps when the connection to the KMS server fails.

What is error code 0x8007232A?​

This is a network error that is caused by the following factors:

  • Incorrect DNS settings on the computer.
  • Problems with the DNS server.
  • Issues with the KMS host server.
  • Other network issues on the computer.
You may consider using the best network adapter driver to limit the possibility of error due to network complications.

How do I fix error code 0x8007232A?​

Before any solutions, try this workaround:

  • Connect your computer to a different ISP or a wired internet connection.
If the error persists, you should try the solutions below.

1. Run the Network troubleshooter​

  1. Press Windows + I to open the Settings app.
  2. On the right pane, click on Troubleshoot.
    0x8007232A
  3. Select Other troubleshooters.
    0x8007232A
  4. Click the Run button for Network and Internet.
    0x8007232A
  5. Finally, apply any recommendations and, if required, restart your computer, then verify it fixes the 0x8007232A error.

2. Allow Key Management Service through Firewall​

  1. Press the Start menu, type Firewall, and click Allow an app through Windows Firewall.
    0x8007232A
  2. Click the Change settings button, and below, click Allow another app.
    0x8007232A
  3. Click the Browse button, then navigate to the path below and select sppsvc.exe (It is responsible for managing software licenses for Microsoft products).
    C:\Windows\System32\
    0x8007232A
  4. Finally, click Add, then click OK.
Alternatively, you may create a new port for KMS with the steps below:

  1. Press the Start menu, type Firewall, and click Windows Firewall with Advanced Security.
  2. In the left pane, select Inbound Rules and click New Rule on the right.
    0x8007232A
  3. Select Port and click Next.
  4. Under Specific Local Ports box, type 1688, then click Next.
    0x8007232A
  5. Select Allow the connection and click Next.
  6. Click Next again, then in the Name box, type TCP-1688 and click Finish.
Read more about this topic

3. Check KMS Host Server for Internet​

  1. Open the Run dialog by pressing Windows + R.
  2. Type cmd and press Ctrl + Shift + Enter to open the Command Prompt with administrator privileges.
  3. Type the script below and hit Enter.
    nslookup kms.windows.com
  4. You should see an IP address; however, if you do not see one, the KMS host server is not connected to the internet, and you may contact Microsoft support.
You should find success using any of the solutions above. We have not written them in any particular order, so you should try whichever seems the most applicable.

In extreme situations, you may consider factory resetting your computer. However, this may lead to the loss of some important files.
 
That's thankfully a pretty obscure problem these days. There was a string of viruses/nasty adware that poisned the DNS that did some nasty redirects to bad places. That was a while ago, but you never know.
One thing I would add is before anything else, open a CMD prompt and Type 'ipconfig /flushdns' in the CMD Prompt, and press Enter. Sometimes that's all you need.
Wow this could open up a discussion on what DNS do you use? I think I may start a new thread for that topic.
 
DNSJumper does that and morfe LOL
That's thankfully a pretty obscure problem these days. There was a string of viruses/nasty adware that poisned the DNS that did some nasty redirects to bad places. That was a while ago, but you never know.
One thing I would add is before anything else, open a CMD prompt and Type 'ipconfig /flushdns' in the CMD Prompt, and press Enter. Sometimes that's all you need.
Wow this could open up a discussion on what DNS do you use? I think I may start a new thread for that topic.
DNSJumper does that and much more :)
 
DNSJumper does that and morfe LOL

DNSJumper does that and much more :)
Hmmmm I don't know about those programs that are scripts that make "safe" changes dynamically behind the scenes. I am not saying Sordum has any bad intentions. It's just another way the a-holes out there can sneak some unwelcome changes with some bad outcomes into your system. There are some real creeps out there always looking for another way to exploit the Internet for their own gain.
 
Back