Our recommendation: Cloudflare DNS
Boost runs on Cloudflare Enterprise. When your DNS is also on Cloudflare, we can set up and manage Boost from start to finish without needing anything from you, and most sites are boosted the same day.
There are a few ways to get there:
Move your DNS to Cloudflare with us. Send us a zone file export from your current DNS provider and we'll import every record into Cloudflare for you. You keep full access to your DNS and can make changes yourself whenever you like.
Use your own Cloudflare account. If you already have one, invite us as a member with permission to manage DNS for your domain and we'll handle the rest.
Keep your current DNS provider and give us access. We'll make the changes there for you. We have guides for sharing access with common providers, including GoDaddy, Namecheap and Squarespace, in our Useful Tools and Tips collection.
Keeping DNS in-house
We understand that not every organization can hand over DNS or switch providers. This is common for larger companies, where DNS is managed by an internal IT team or tied to other systems. Boost still works in that case. The setup just happens in two steps, and you (or your IT team) make the DNS changes when we ask.
Before you start: canonical and non-canonical
Every site has two main addresses, the one with www and the one without. Your canonical domain is the one your site actually uses. The other is the non-canonical domain, and it redirects visitors to the canonical one.
For example, if your site loads at https://example.com, then:
example.com is your canonical domain
www.example.com is your non-canonical domain
If you're not sure which one you use, visit your site and look at the address bar after the page loads. We'll also confirm it with you before you change anything.
Step 1: Point both records to your server
First, point both the canonical and non-canonical records to your BigScoots server IP, the same way you would with any web host. We'll send you the server IP.
Both records must be A records.
Don't set the non-canonical record up as a CNAME pointing to the canonical one. It has to be its own A record.
Remove any other A or AAAA records on these two names that point somewhere else, such as a previous host.
Let us know once the records are updated. We'll check that your site is loading correctly from our server and set up its SSL certificate there. This lets us validate your domain with Cloudflare before any traffic is routed through Boost.
Please wait for us to confirm before moving on to Step 2. Skipping ahead can stop the SSL certificate from being issued on the server (more on that in the FAQ below).
Step 2: Point the canonical record to Boost
Once everything is validated and Boost is active on our end, we'll let you know it's time for Step 2.
Update your canonical record only, replacing the server IP with these two A records:
216.185.212.56
216.185.212.57
Leave the non-canonical record pointed at your server IP, exactly as it was in Step 1.
Let us know once the change is made, and we'll check that everything is working as expected through Boost.
What your records should look like
Using example.com as the canonical domain:
Record | Type | Step 1 | Step 2 |
example.com (canonical) | A | Server IP | 216.185.212.56 and 216.185.212.57 |
www.example.com (non-canonical) | A | Server IP | Server IP (no change) |
If your site uses www.example.com as the canonical domain, swap them: www.example.com gets the two Boost IPs, and example.com stays an A record pointed at your server IP.
Why does the non-canonical record stay pointed to the server?
The non-canonical domain only exists to send visitors to the right address. Any visit to it reaches your server, which immediately redirects it to your canonical domain. That request then goes through Boost like every other visit.
So all real page traffic still ends up going through Cloudflare Enterprise, while the redirect is handled directly by your server.
FAQ
Why can't I point straight to the Boost IPs?
Your server needs its own SSL certificate as well as the one Boost uses, and the server can only issue it while your domain is pointed at the server. If the records are already pointed at Boost when we try, the certificate on the server can fail. That's why Step 1 has to be finished and confirmed first.
I already pointed my records to the Boost IPs. What now?
Let us know right away. We'll try to issue the server certificate anyway, which sometimes works but can take a while. If it doesn't go through, we'll ask you to point the records back to the server IP for a short time, then switch the canonical record back to the Boost IPs once the certificate is in place.
Why can't the non-canonical record be a CNAME?
A CNAME makes one name follow another. If the non-canonical record were a CNAME to your canonical domain, it would follow it to the Boost IPs in Step 2 instead of reaching your server, and the redirect wouldn't be handled properly. An A record keeps it pointed at your server.
Do I need to change my email (MX) records or anything else?
No. Only the two records above change. Your MX, SPF, DKIM, TXT and other records stay exactly as they are.
Is there anything I can do to make the switch faster?
If your DNS provider lets you set a TTL, lowering it to 5 minutes (300 seconds) on these two records a day before you start helps changes show up sooner. You can raise it again once Boost is live.
Can I move my DNS to Cloudflare later?
Yes. Open a ticket whenever you're ready and we'll take you through it, including importing your existing records.
What if we change DNS providers or need to edit these records later?
Please contact us before changing the canonical or non-canonical records, or before moving to a new DNS provider. Pointing either record somewhere else can take your site off Boost or stop it from loading, and we're happy to make sure the change goes smoothly.
I already use my own Cloudflare account. Does that change anything?
It makes things easier. Invite us as a member on your account with DNS permissions for the domain and we can manage the Boost setup directly, without the two-step process. If you have your own Cloudflare rules or tools that need to run in front of Boost, mention it in your ticket and we'll go over the options.