How to fix Windows activation error 0x8007251D?

Error 0x8007251D, "No records found for DNS query", means Windows is set up for company activation through a Key Management Service (KMS) host, and DNS has no record of one. After a home reinstall, that almost always means a volume key or edition was installed. Run slmgr /dli first to see which licence Windows holds.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What Windows activation error 0x8007251D means

Microsoft's list of activation error codes names it "0x8007251D No records found for DNS query" and marks it as a KMS client error. The cause it gives is short: the KMS client cannot find the KMS SRV records in DNS.

A PC with a KMS client key does not activate with Microsoft directly. It asks its DNS server for a _vlmcs._tcp service record that names the organisation's KMS host and port 1688. With 0x8007251D, the DNS server replied, but it has no such record for the PC's domain. A home router never has one.

Why error 0x8007251D appears, from most to least common

The code comes from where Windows looks for activation, not from damaged files or a weak connection. Find the row that matches your PC and go to its fix.

The old advice for this code was a better internet connection, repair tools and patience. Microsoft's own entry points to DNS and KMS only. A home PC with a working connection still fails, because no home DNS server holds a KMS record.

How to fix Windows activation error 0x8007251D

Fix 1 shows which licence Windows holds. Fixes 2 and 3 are for home PCs, Fix 4 for work and school PCs. Fixes 5 to 7 are for the IT admin and follow Microsoft's DNS and KMS procedures. Fix 8 is for a genuine purchase that still fails.

Fix 1. Check which licence Windows holds with slmgr /dli

2 minutesNo riskEveryone, first. It takes a minute and decides which fix is yours.

Windows looks up KMS records in DNS only when a KMS client key is installed. The licence channel in this box shows that at once, and the edition name shows whether the reinstall used the wrong media.

1. Open Start, type cmd, right-click Command Prompt and select Run as administrator.
2. Select Yes in the User Account Control window.
3. Type slmgr /dli and press Enter.
4. Read the Name and Description lines in the Windows Script Host box.
5. Select OK to close it.

If the Name line says Enterprise or Education and your licence is for Home or Pro, the reinstall used the wrong edition. Your own key cannot activate it until the edition matches.

Fix 2. Replace the volume key with your own product key for the same edition

3 to 5 minutesNo riskHome PC with VOLUME_KMSCLIENT in Fix 1, and you have a genuine key for the same edition.

Your retail or OEM key replaces the KMS client key. Windows then activates online with Microsoft and stops asking DNS for a KMS host, so the missing record no longer matters.

1. Open Settings > System > Activation (Windows 10: Settings > Update & Security > Activation).
2. Select Change product key. Windows may ask for an administrator password.
3. Type your 25-character key and select Next.
4. Select Activate and wait for the page to update.
5. Run slmgr /dli again. The channel should now be RETAIL or OEM.

The same in Command Prompt as administrator takes two commands, and the error text is clearer when it fails.

Install your own key and activate online

slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato

Fix 3. Restore your digital licence with the Activation troubleshooter

5 to 10 minutesNo riskHome PC that was activated before the reinstall, through a free upgrade, a Store purchase or a preinstalled licence, and you have no key.

A digital licence is stored with Microsoft for this hardware and often for your Microsoft account. While a KMS client key is in place, Windows keeps searching DNS instead. The troubleshooter looks up the licence for the device and can put the right key back.

1. Make sure the PC is online, since the troubleshooter checks with Microsoft: How to check your internet connection in Windows
2. On Windows 11, run the Windows Activation troubleshooter in the Get Help app, which is Microsoft's first advice for activation errors. You can also open Settings > System > Activation and select Troubleshoot.
3. On Windows 10, open Settings > Update & Security > Activation and select Troubleshoot.
4. If it asks you to sign in, use the Microsoft account you used on this PC before.
5. If it finds the licence, follow its prompt to activate.

Fix 4. Work or school PC: connect to the work network or VPN, then activate

5 minutesNo riskThe PC belongs to an employer or school, shows VOLUME_KMSCLIENT, and is used away from the office.

The _vlmcs._tcp record lives in the company's DNS. At home the PC asks the router's DNS, which answers that it has no such record: exactly 0x8007251D. Microsoft says a work device that is not connected to the workplace network shows this group of errors.

1. Connect to the office network, or start the company VPN.
2. Open Command Prompt as administrator (Fix 1).
3. Type slmgr /ato and press Enter.
4. If the code comes back, send a screenshot and the PC name from Settings > System > About to your IT team.

Activate once you are on the work network

slmgr /ato

Microsoft adds that if you are on the work network and still see the error, the network settings may need a change by your organisation's support person. Without a support person, it suggests entering your product key again (Fix 2).

Fix 5. IT admin: test whether the problem is the SRV record or name resolution

10 minutesLow riskYou run the KMS host, and clients on the work network show 0x8007251D.

Microsoft's DNS procedure uses this test to split the problem. If naming the host by FQDN works, the SRV record is missing. If only the IP address works, name resolution is broken. If neither works, a firewall blocks port 1688.

1. On the client, open Command Prompt as administrator.
2. Run ping with the DNS server's IP address. No "Reply from" line means a network or DNS problem to solve first.
3. Run slmgr.vbs -skms with the KMS host's full name and port, then slmgr.vbs -ato, as in the first block below.
4. If that worked, the SRV record is the problem: go to Fix 6. You can leave the host set for now.
5. If it failed, repeat with the host's IP address, as in the second block. Success now means a name resolution problem.
6. If both failed, allow TCP port 1688 in the firewalls on the client and on the KMS host.
7. When DNS is fixed, run slmgr.vbs -ckms to return the client to automatic discovery.

Name the KMS host by its full name

cscript \windows\system32\slmgr.vbs -skms kms01.contoso.com:1688
cscript \windows\system32\slmgr.vbs -ato

Name it by IP address, then return to automatic discovery later

cscript \windows\system32\slmgr.vbs -skms 10.0.0.15:1688
cscript \windows\system32\slmgr.vbs -ato
cscript \windows\system32\slmgr.vbs -ckms

Fix 6. IT admin: publish the _vlmcs SRV record in the client's DNS zone

15 to 30 minutesRead the warningNaming the host by hand in Fix 5 works, but automatic discovery returns 0x8007251D.

This is the exact case behind the code: the client's zone has no _vlmcs record. Microsoft explains that a KMS host registers its record only in its own domain's zone, every 24 hours, unless publishing is off. Clients in another zone, or a DNS server that refuses updates, find nothing.

1. On a client, run nslookup -type=all _vlmcs._tcp>kms.txt and open kms.txt.
2. A good entry reads _vlmcs._tcp.contoso.com SRV service location with port = 1688 and the host name. Check that its domain is the client's domain.
3. Check that the client's primary DNS suffix search list contains the KMS host's domain.
4. Back up the registry on the KMS host: Back up the registry before editing it
5. On the KMS host, open regedit at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform and check DisableDnsPublishing: 0 or missing publishes, 1 does not.
6. If clients use other DNS domains, add a Multi-String value DnsDomainPublishList there with one domain per line, then restart the Software Protection service.
7. If your DNS server refuses dynamic updates, create the record by hand: service _VLMCS, protocol _TCP, port 1688, host = the KMS host's full name.
8. On a client, run slmgr.vbs -ckms to clear any cached host, then slmgr /ato.

Look for the KMS record from a client

nslookup -type=all _vlmcs._tcp>kms.txt
notepad kms.txt

Fix 7. IT admin with no KMS host: activate with a MAK key

5 minutes per PCNo riskYour organisation installed volume media but runs no KMS host.

Without a KMS host, no DNS record can ever exist, so 0x8007251D will not go away. For the same DNS family, Microsoft's alternative is a Multiple Activation Key (MAK), which activates each PC online with Microsoft.

1. Get the MAK for the installed edition from your organisation's volume licensing account.
2. Open Command Prompt as administrator.
3. Install the MAK with slmgr /ipk.
4. Activate with slmgr /ato.

Install the MAK and activate

slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
cscript \windows\system32\slmgr.vbs /ato

Fix 8. Contact Microsoft support with proof of a genuine purchase

15 to 30 minutesNo riskYou bought Windows from Microsoft or an authorised seller, and Fixes 2 and 3 did not activate it.

Support can look up your purchase and the state of your key, which nothing on the PC can show. If your key turns out to be a volume key, only the seller or Microsoft can sort that out.

1. Collect the order number or email, the account used to buy, and a photo of any key card.
2. Take screenshots of the Activation page and of the slmgr /dli box.
3. Check the PC's date, time and time zone: How to fix the date and time in Windows
4. Open support.microsoft.com/contactus and choose Windows activation.
5. Say that the error is 0x8007251D and which channel slmgr /dli showed.

If error 0x8007251D is still there

Collect these facts before you ask your IT team or Microsoft. Together they show whether the key, the network or DNS is at fault.

How to avoid error 0x8007251D next time

At home, the error starts with volume media or a volume key. In a company, it starts with a DNS zone that has no KMS record.

Frequently asked questions

What does error code 0x8007251D mean?

It means Windows tried to activate through a company Key Management Service host and the DNS server had no record for one. Microsoft's text is "No records found for DNS query." Nothing on the PC is broken. On a home PC it means a volume key or Enterprise edition is installed. On a work PC it means the company DNS, and its _vlmcs._tcp record, cannot be reached.

Why do I get 0x8007251D right after reinstalling Windows?

Most often the install media was an Enterprise or volume edition, or a KMS client key was typed during setup. Windows then searches DNS for a KMS host that a home network never has. Check the edition in Settings > System > About and run slmgr /dli. If the edition is not the one you bought, reinstall from Microsoft's own media, pick your edition and activate with your key or digital licence.

What is the difference between 0x8007251D and 0x8007232B?

Both are KMS client errors about DNS. Microsoft's text for 0x8007232B is "DNS name does not exist", and for 0x8007251D it is "No records found for DNS query." In both cases the client cannot find the KMS SRV records, and the fixes are the same. Read our 0x8007232B guide if your screen shows that code instead.

How do I fix 0x8007251D on Windows 11?

Open Command Prompt as administrator and run slmgr /dli. If it shows VOLUME_KMSCLIENT on a home PC, open Settings > System > Activation > Change product key and enter your own key for the same edition. With no key, run the Activation troubleshooter in the Get Help app. On a work PC, connect to the work network or VPN and run slmgr /ato.

Is 0x8007251D on Windows 10 the same error?

Yes. The code, the cause and the fixes are the same on Windows 10 22H2. Only the menu differs: Settings > Update & Security > Activation instead of Settings > System > Activation. Windows 10 left support on 14 October 2025 and gets no more security fixes, but activation with a valid key works as before.

Will a better internet connection fix 0x8007251D?

Usually not. The PC needs to be online, but the error comes from the DNS answer, not from the speed or stability of the link. A home router can answer every web request and still have no KMS record. Changing the key on a home PC, or reaching the company DNS on a work PC, is what removes the code.

Can I just wait and try activating again later?

The message on the Activation page says you can try again later, but with 0x8007251D waiting does not help. The PC is not waiting for a busy Microsoft server. It is asking DNS for a KMS host that is not listed. Until the key changes, or the PC reaches a DNS server with the record, every attempt returns the same code.

Can I use a generic or default product key to get past 0x8007251D?

No. Microsoft's public KMS client setup keys activate only against a KMS host, so on a home PC they cause this very error. Older guides suggested them; this page does not. Use the key you bought or your digital licence (Fix 2 and 3). A work PC needs the company network, not another key.

Is there a way to bypass error 0x8007251D?

There is no safe bypass. Tools that promise free activation install a KMS client key and point Windows to an unofficial host; when that host is gone, this error returns. They also change system files and run with full rights, so this page does not link to any. The way through is a genuine key, a restored digital licence, or the work network.

What does an Event Viewer entry with hr=0x8007251D mean?

It is the same error written to the Application log. slui.exe, the Windows activation client, tried to activate in the background and DNS returned no KMS host. Use the same fixes as for the Activation page. We could not confirm the exact event ID in Microsoft's documentation, so search the log for the code.