RebelSites runs on Cloudflare infrastructure, which can create a conflict when your domain’s DNS is also managed by Cloudflare. The good news: RebelSites detects this automatically and handles it for you. No manual nameserver changes are needed.
When you add a custom domain, RebelSites checks whether your domain uses Cloudflare nameservers. If it does, the system automatically routes your apex domain (e.g., yourbusiness.com) through an alternative bridge that avoids the Cloudflare-on-Cloudflare conflict. Here’s what that means in practice:
Your www subdomain (e.g., www.yourbusiness.com) connects through the standard path — no conflict there.
Your apex domain (e.g., yourbusiness.com) is routed through a separate bridge that redirects visitors to the www version automatically.
SSL is automatic — a certificate is issued for both the apex and www, just like any other domain.
Entri still works — the DNS configuration modal handles everything the same way.
Nothing different. Connect your domain the same way you would any other domain — follow the steps in our "Connecting a custom domain" article. RebelSites detects the Cloudflare DNS and applies the workaround transparently.
Visitors to your site won’t notice any difference. Both yourbusiness.com and www.yourbusiness.com will load your site with full HTTPS. The only thing that changes is the infrastructure path behind the scenes.
In rare cases, the automatic bridge setup may not complete. If you see an error when connecting a Cloudflare-hosted domain, tap the chat icon and our team will sort it out.
