Fix DNS_ERROR_DP_DOES_NOT_EXIST (0x26AD) in Windows Server

This error pops up when you try to delete a DNS directory partition that's already gone or never existed. Here's why it happens and how to clean it up for good.

When This Error Hits

You're on a Windows Server DNS admin console or running dnscmd, and you try to delete a directory partition that you created earlier for DNS zone replication. The command fails with DNS_ERROR_DP_DOES_NOT_EXIST (0X000026AD). This usually happens right after you've removed a DNS zone or demoted a domain controller, but the partition entry lingers in the DNS service's internal state. The partition itself is gone from Active Directory, but the DNS server still thinks it's there—or the reverse: the partition object exists in AD but the DNS service can't see it.

I've seen this most often on domain controllers that were repurposed or when someone manually deleted a _msdcs or a custom application partition without cleaning up the DNS references. It's a classic orphaned-object situation.

Root Cause in Plain English

DNS directory partitions live in Active Directory as applicationPartition objects. When you delete a DNS zone, the zone is removed, but the partition that hosted it isn't automatically deleted—especially if the partition is still referenced by any zone or if the deletion order got messed up. The DNS service keeps a local cache of known partitions. When you try to delete a partition that's not in that cache or not in AD, you get 0x26AD. The error literally means "the specified directory partition does not exist," which is Microsoft's way of saying the object you're pointing at isn't there from the system's perspective.

What's actually happening here is a mismatch between three places: Active Directory (the source of truth), the DNS service's in-memory list, and the registry (where the DNS service stores its partition list). If any one of those gets out of sync, you'll see this error.

The Fix: Step-by-Step

This fix assumes you're on Windows Server 2016 or later, but it works on 2012 R2 too. You need Domain Admin rights.

Verify the partition is truly gone from AD. Open an elevated PowerShell and run:
```
Get-ADObject -Filter 'objectClass -eq "applicationPartition"' -SearchBase "" | Select-Object Name, DistinguishedName
```
If your partition isn't listed, it's already deleted from AD. If it is, you'll need to delete it with Remove-ADObject—but only after confirming no DNS zones reference it.
Check DNS zones still pointing to the partition. Run:
```
dnscmd /enumzones
```
Look for any zone whose replication scope is that partition. If you find one, either delete the zone or change its scope with dnscmd /zonechangedirectorypartition.
Remove the partition using dnscmd. The official way is:
```
dnscmd <DnsServerName> /deletedirectorypartition <FQDN of partition>
```
If this returns 0x26AD, you've hit the exact bug. The partition is gone from AD but the DNS service still has it cached.
Clear the DNS service's partition cache. Stop the DNS service:
```
Stop-Service DNS
```
Then edit the registry. Go to HKLM\SYSTEM\CurrentControlSet\Services\DNS\Parameters\ZoneList and find any entry that matches your partition's FQDN. Delete that value. Be careful—this key also holds zone names, so only remove the partition entries you're cleaning up.
Restart DNS and verify.
```
Start-Service DNS
```
Now try the delete again:
```
dnscmd /deletedirectorypartition <FQDN>
```
It should succeed or return a benign error like "partition not found," which is fine because it's already gone.
If you're feeling brave, use ADSI Edit. Sometimes the partition object is still in AD but hidden. Open ADSI Edit, connect to Configuration, and navigate to CN=Partitions,CN=Configuration,DC=yourdomain. Delete the CN=<partition> object there. This is the nuclear option—make sure you're not deleting the default partitions (DomainDnsZones, ForestDnsZones).

What to Check If It Still Fails

If the error persists, you're not dealing with a simple cache issue. Check a few things:

Replication latency. If you're on a multi-DC environment, the partition deletion might not have replicated to the DC you're working on. Force replication with repadmin /syncall /AdeP and wait a few minutes.
Read-only domain controllers (RODCs). RODCs don't hold application partitions by design. If you're trying this on an RODC, you'll get 0x26AD because the partition never existed there. Run the command on a writable DC.
DNS scavenging tasks. Check if there are any scheduled tasks or scripts that still reference the partition name. A leftover script running dnscmd /enlistdirectorypartition on boot can recreate the partition after you delete it, causing the error to reappear.
Event logs. Look for Event ID 1009 or 4004 in the DNS server log. They often give the exact partition name and the DC that's causing the problem.

The registry tweak in step 4 is the real fix here. Without it, you'll keep hitting the error because the DNS service re-reads the stale entry on every start. I've seen admins waste hours trying to delete a partition that was already deleted—this clears the ghost.