How to Fix Cloudflare Error 1105 (Authoritative DNS / ‘This zone is temporarily restricted’)

Quick Fix

If you are trying to add or move a domain’s DNS to Cloudflare and see ‘Error [1105]’, this almost always means Cloudflare has temporarily flagged the zone after repeated add attempts, or DNSSEC at your registrar is blocking Cloudflare from becoming authoritative. Try this first:

1. Stop retrying immediately. Repeated attempts extend the restriction. Wait at least 3 hours, then try adding the domain again.
2. Disable DNSSEC at your old registrar/DNS provider before switching nameservers to Cloudflare, since an active DNSSEC/DS record will block Cloudflare from generating authoritative DNS for the zone.
3. Confirm the domain has valid NS and SOA records using a tool like whatsmydns.net before re-adding it.

If instead you are just a visitor seeing ‘Error 1105: Temporarily unavailable’ on someone else’s website, this is a server-side origin issue you cannot fix yourself — wait a few minutes and reload, or contact the site owner.

Step-by-Step Guide

What Cloudflare Error 1105 means

Error 1105 is a generic Cloudflare error code that actually covers two unrelated situations. Figuring out which one you have is the key to fixing it fast.

1. Zone/DNS setup error (site owners): When adding a domain to Cloudflare, you may see: Error with Cloudflare request: [1105] This zone is temporarily restricted and cannot be added to Cloudflare at this time, please contact Cloudflare Support. This is the ‘Authoritative DNS Generation’ style error — Cloudflare cannot generate/activate authoritative DNS for your zone right now.
2. Visitor-facing website error: The Error 1105 while visiting a site protected by Cloudflare is a different error than the zone-add restriction message. It normally reads ‘Temporarily unavailable’ and is shown to ordinary visitors, not the site owner, when their origin server misbehaves.

Case A: You are adding/migrating a domain and get ‘[1105] This zone is temporarily restricted’

This is triggered by rate limiting, not a bug on your end.

1. Identify the cause. Cloudflare returns this because it has seen too many attempts to add a domain to Cloudflare.
2. Wait it out. The resolution is to wait 3 hours before attempting to re-add the domain, and Cloudflare support cannot speed up this process. Do not keep clicking ‘Add Site’ repeatedly — that resets the clock.
3. Check for DNSSEC conflicts. Cloudflare cannot provide authoritative DNS resolution for a domain on a primary (full) setup when DNSSEC is enabled at your domain registrar. Symptoms of this include: DNS does not resolve after switching to Cloudflare’s nameservers, DNS query response status is SERVFAIL, and the domain remains in a Pending status. Log in to your old registrar and disable DNSSEC before (or immediately after) pointing nameservers to Cloudflare.
4. Verify NS and SOA records are valid. Before a domain can be added, the domain must return NS records for valid, working nameservers, and must also return a valid SOA record when queried. You can check these with a dig command or an online DNS lookup tool.
5. Rule out an apex/subdomain mistake. A related error, Code 1093, happens because you may have entered a subdomain like www.example.com instead of the apex (root) domain, and the resolution is to verify you are entering the apex domain.
6. Check for a zone hold. If your organization uses Enterprise zone holds, you may see: The zone name provided is subject to a hold which disallows the creation of this zone, and you should contact the owner of the Cloudflare account that manages this domain to have the hold removed.
7. Still stuck after 3+ hours and a clean DNS check? Contact Cloudflare Support directly — this is a Cloudflare-side restriction that only their team can lift for permanent bans or unusual domains (e.g. .gov TLDs needing manual registration).

Case B: A visitor sees ‘Error 1105: Temporarily unavailable’ on a website

This is almost always an origin-server problem, not something the visitor can fix.

1. Bypass Cloudflare to confirm the source. The first step in fixing this error is to find if it is actually related to Cloudflare, by checking whether the issue can be replicated when you bypass Cloudflare.
2. Check for a 503 from the origin server. Another common reason for this error is a 503 coming from the origin server — if it is a WordPress site, a possible reason could be that the site is currently in maintenance mode, and Cloudflare sees the 503 error code as a server error and returns 1105.
3. Consider server overload. This could also happen when the origin server is overloaded, and a proper analysis of the server logs is important to recognize the exact reason. As a site owner, check CPU/memory usage and database health.
4. Rule out a restrictive network. The 1105 error can also trigger due to restrictions in the network settings — a restrictive network tends to block some websites, and using an unfiltered network may help fix the issue. Try a different Wi-Fi network, mobile data, or a VPN.
5. Check Cloudflare’s own status. Occasionally 1105 spikes are caused by Cloudflare-side incidents rather than your site. In one documented case, a batch of 1105 errors correlated with a Cloudflare status page report of increased 5xx errors, and Cloudflare support confirmed the 1105 errors were indeed related to that incident. Check cloudflarestatus.com if the error appeared suddenly across many users.
6. As the site owner, if you just migrated servers: confirm your Cloudflare DNS records point to the new origin IP, and confirm the new origin actually responds to requests directly (not just through the proxy) before assuming it’s a Cloudflare bug.

Case C: You saw this on Discord specifically

Discord runs behind Cloudflare, so ‘Cloudflare server error 1105’ occasionally appears there too, usually tied to Discord’s own infrastructure rather than your device.

1. Check Discord’s status page at discordstatus.com for active incidents before troubleshooting locally.
2. Restart the app and your router. This clears stuck connections and re-establishes a fresh route to Discord’s servers.
3. Try a VPN or different network to rule out local network filtering (common on school/work networks).
4. Clear Discord’s cache by opening %AppData%discord via Run (Windows key + R), then deleting the contents of the Cache and Local Storage folders, and restarting Discord. This is Windows-specific; on Mac or mobile, use the app’s built-in ‘clear cache’ option in Settings if available.

When to escalate to official support

If you are a domain owner and the zone restriction persists well beyond 3 hours, or you get errors referencing a permanent ban, zone hold, or unregistered/.gov domain, this needs Cloudflare Support directly rather than further self-troubleshooting — these restrictions are enforced on Cloudflare’s backend and cannot be cleared by end users. If you are a visitor and the site-wide 1105 error persists for hours across multiple networks, it is a hosting/origin issue for the site owner to resolve, not something fixable from the visitor’s side.