Why Cloudflare? #
We were moving our static sites away from Netlify anyway and it did not make sense to keep it just for the basic DNS it provides.
Why not Route53? #
We have the rest of the infra on AWS, so Route53 would have made some things easier. But all eggs in one basket ¯\_(ツ)_/¯
How hard was it? #
The hardest part was moving all of the DNS records. Cloudflare tries to scan for and automatically add existing records, but it missed most of our records - especially CNAME records. It did get the MX records right.
The only way to add records - other than manually adding each one - is to use a zone file. The problem now was that Netlify DNS could not export records to a zone file. What it did provide was an API to list all records. So I used the data from this API to programmatically generate a zone file.
I have open sourced this tool here: Netlify DNS Zone File Generator
Then we simply imported this zone file in Cloudflare. We changed the nameservers in our domain registrars to Cloudflare’s and it took less than 30 mins for them to verify it - Cloudflare notes that this can take up to 24 hours.
Cloudflare enabled proxying by default for the imported records, so we did not have to do anything more to enable the CDN and reverse proxy. So all good then?
Nope. Our websites were not working in certain browsers - it showed an SSL/TLS error.
Your website was down??? #
So Cloudflare has an SSL/TLS mode called “Flexible” which, apparently, “Encrypts traffic between the browser and Cloudflare”. Turns out that it’s not really flexible. It adds its own SSL/TLS on all proxied domains and that caused a problem. We changed the mode to “Full” which just means that the servers manage their own SSL/TLS.
I’m not really sure what the exact issue here was, but I would be interested in figuring it out.