Knowledge base

A network would not accept my domain: how to choose another network

Sometimes a CDN or DNS network refuses a particular domain. Nothing is deleted: pick another network on the site and it is built there in one click.

Every site is served through a CDN (content delivery network), and its domain's DNS is hosted by a DNS network. Very occasionally a network refuses a particular domain. When that happens the site cannot be built on that network however long it waits, so we stop straight away and ask you to choose another network.

What you see

The site shows as failed, with a yellow box at the top of its page:

Cloudflare would not accept example.com — choose another network

The network is named when it is the one you chose for the site. If the platform chose it for you, the box says the network this site was set up on. Under it is the reason in plain words, and one button for each other network your account can use: Use Bunny CDN, Use Gcore, and so on.

Why a network can refuse a domain

  • It will not carry that domain name. Some networks decline certain names or domain endings.
  • That is the network's own decision and it cannot be changed from our side.

  • It cannot find the domain at its registry. The domain may not be registered yet, may have
  • expired, or may be spelled differently. Check it at your registrar.

  • Another account at that network already holds the domain. For example, the domain is still
  • added to someone else's account at that network.

  • It only accepts a main domain (like example.com), not a subdomain.
  • Its certificate authority will not issue a certificate for the domain.

None of these is a fault with your site or with our hosting.

How to choose another network

  1. Open Sites and choose the site.
  2. In the yellow box, press Use and the network you want.
  3. The site is built again from the start on that network. It takes a few minutes. If the new
  4. network needs new nameservers, the site then shows them, exactly like a new site.

Nothing on your site is deleted, and you do not need to delete and re-create it. The DNS moves off the network that refused the domain at the same time, so the new build does not fail the same way.

If no other network is offered

The box says so. Open a support ticket from the site page and we will help you put the site live.

Latest from the blog

What we have been writing about hosting, SEO and running sites at scale.

SEO and Link Building from the Hosting Layer: A 2026 Operator's View

How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.

Read the post →

Making WordPress Fast and Secure: A Performance and Plugin Checklist

A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.

Read the post →

How to Choose Managed Web Hosting in 2026: A Buyer's Guide

What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.

Read the post →

Read the blog →

Still stuck?

Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.

Contact support → All articles →