0X00002595

DNS Zone Shutdown Error 0X00002595: Fix It Now

EP
Erropedia Team
📅 May 26, 2026 📅 Updated Jul 31, 2026 👁 9 views Network & Connectivity Intermediate
DNS zone won't load because it's shut down. Quick fix: restart the DNS service or re-enable the zone. Common on Windows Server.

It's a pain when DNS stops responding

You're staring at Event Viewer or a command prompt, and there it is — DNS_ERROR_ZONE_IS_SHUTDOWN (0X00002595). The zone you need just won't load. Yeah, I've been there. Had a law firm's internal DNS die last year because a junior admin accidentally disabled the primary zone. Let's get this fixed.

How to fix it — the real fix

Step 1: Restart the DNS service

Before you do anything else, restart the DNS server service. This often clears the shutdown flag.

  1. Open Services.msc
  2. Find DNS Server
  3. Right-click and select Restart

Or from an admin command prompt:

net stop dns && net start dns

After restart, check if the zone loads. Use dnsmgmt.msc or dnscmd /enumzones to confirm the zone is listed as running, not paused or shutdown.

Step 2: Check the zone status

If restarting didn't work, the zone is likely disabled at the configuration level. Open DNS Manager:

  1. Right-click on the server, select Properties
  2. Go to the Advanced tab
  3. Under Zone Loading, make sure it's set to Load on startup

Then manually enable the zone:

dnscmd /ZoneResetType [zone-name] /Primary

Replace [zone-name] with your actual zone (e.g., contoso.local). This forces the zone to re-read from AD or file.

Step 3: Check registry (advanced)

In stubborn cases, the registry stores a shutdown flag. This is rare but I've seen it after a botched domain controller promotion.

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DNS Server\Zones\[zone-name]

Look for a Shutdown DWORD (value 1). Delete it or set it to 0, then restart DNS service again.

⚠️ Don't monkey with the registry unless you know what you're doing. Backup first.

Why does a DNS zone shut down?

The error means the DNS server explicitly disabled the zone. It's not a crash — it's a flag that says "don't serve this zone." This usually happens when:

  • Zone file corrupt or missing — DNS server tries to load it, fails, and marks the zone as shutdown
  • Active Directory replication issue — AD-integrated zones can't load if the DC can't sync
  • Manual disabling — Someone used dnscmd /ZoneShutdown or unchecked the zone in DNS Manager
  • DNS server service stops unexpectedly — On restart, the zone doesn't reinitialize properly

In my experience, 8 times out of 10 it's a corrupt zone file. Check the %systemroot%\system32\dns folder for the zone file (e.g., contoso.local.dns). If it's 0 bytes or missing, you need to restore from backup or rebuild.

Variations of this issue

Event ID 4015

Often paired with error 0X00002595. You'll see "The DNS server has encountered a critical error from the Active Directory." This means the zone is AD-integrated and DNS can't read the directory partition. Fix: check AD health with dcdiag /test:dns and repadmin /replsum. If AD is broken, fix that first.

Zone shows as "Paused" instead of shutdown

Similar but different. A paused zone can be resumed from DNS Manager (right-click → Resume). A shutdown zone won't show up in the list at all. If it's paused, you can also run dnscmd /ZoneResume [zone-name].

Read-only domain controllers (RODC)

On an RODC, you can't create or modify zones. If you see this error on an RODC, the zone is replicated from a writable DC. The fix is to force replication from the main DC or demote/re-promote the RODC.

How to stop it from happening again

  • Monitor zone health — Use dnscmd /statistics or set up alerts for DNS events 4015, 4000, and 409
  • Keep backups of zone files — Script a daily export of all zones using dnscmd /ZoneExport
  • Never manually shut down a zone — I've seen admins do it "temporarily" and forget. Use zone transfer or delegation instead
  • Check permissions on the DNS folder — The DNS service account needs write access to %systemroot%\system32\dns. If that's lost, zones can't load
  • Run regular AD health checks — A lot of DNS issues trace back to replication or NTDS problems

I can't stress this enough: if this keeps happening on the same zone, something is systematically wrong. Either the zone file is corrupting regularly, or there's a hardware issue with the disk. I had a client whose DNS zone kept dying — turned out their C drive was a failing SSD. Replaced it, problem gone.

That's it. Restart DNS, check the zone config, and if that doesn't work, dig into the registry or AD health. You'll have it fixed in 10 minutes.

Related Errors in Network & Connectivity
0X00000254 Fix ERROR_LOST_WRITEBEHIND_DATA (0x254) Delayed Write Failed 0XC00D00D3 HTTP Error 0XC00D00D3: Protocol Not Enabled – Fix It Fast 0X00002728 WSAEMFILE 0X00002728: Too many open sockets fix 0X800401E0 MK_E_CONNECTMANUALLY 0x800401E0: Moniker Fix
DNS_ERROR_ZONE_IS_SHUTDOWN 0X00002595 DNS zone shutdown Windows DNS server DNS service restart zone reload dnsmgmt.msc DNS troubleshooting zone failed to load DNS server not responding zone disabled DNS error 0x2595

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.