CoreSpeed supports two Cloudflare configurations.
Option 1: SiteCare-managed Cloudflare zone
The domain’s authoritative nameservers point to a zone in SiteCare’s Cloudflare account.
SiteCare manages:
- Cloudflare Workers and routes
- CoreSpeed caching
- Proxy configuration
- Origin routing
- Performance and security rules
- Production cutovers
- Website-related DNS changes
Your organization receives Administrator-level access to its zone, including full DNS management capabilities.
You retain control over DNS records for services such as:
- Microsoft 365 or Google Workspace
- Email authentication
- Third-party applications
- Domain verification
- Subdomains
- Customer portals
- Other external systems
Changing authoritative nameservers does not transfer domain registration or ownership. It changes which DNS provider holds and answers with the authoritative records for the domain.
This is SiteCare’s standard and preferred CoreSpeed configuration because it gives us a clear responsibility boundary for the website delivery stack.
Option 2: Customer-owned Cloudflare with O2O
Organizations that already have a Cloudflare account can retain it through an Orange-to-Orange, or O2O, configuration.
Traffic passes through two Cloudflare zones:
Visitor → customer Cloudflare zone → SiteCare Cloudflare zone → CoreSpeed origin
The customer’s zone remains authoritative. A proxied CNAME sends website traffic through the SiteCare Cloudflare for SaaS configuration. Cloudflare applies the customer-zone settings first and the SiteCare-zone settings second.
SiteCare requires Super Administrator - All Privileges access to the customer’s Cloudflare account for this configuration.
O2O is most appropriate when an organization:
- Has an established Cloudflare governance program
- Manages several applications in one Cloudflare account
- Uses account-level Cloudflare services
- Has internal policies preventing nameserver delegation
- Needs its IT team or MSP to retain primary ownership of the zone
Selecting the right option
The SiteCare-managed option provides the simplest support model.
O2O provides greater customer control, but it also requires coordination because settings in the customer zone can change, override, or conflict with the CoreSpeed delivery configuration.
Comments
0 comments
Please sign in to leave a comment.