Today, we’re excited to be rolling out a change to how Cloudflare works for customers. In the past, we distributed a CNAME record (
app.bubble.io) that users had to ALIAS or CNAME to from their registrar. Many registrars don’t support ALIAS records, and that made using custom domains difficult.
Today, we’re launching a new version of the Cloudflare feature that uses A records. When you register a new custom domain, you’ll be given two records of the form
220.127.116.11 that can be entered directly as A records at your registrar, without changing your nameservers or your custom domain.
Q. My custom domain is pointed to
app.bubble.io. Do I have to change my records?
app.bubble.io will continue to work for the indefinite future.
Q. There are two different A records. Do I have to use both?
A. No, one or the other, or both, should work identically. We provide two records for the sake of reliability: in the unlikely event that a particular address is unavailable, your customers’ browsers would be able to fall back to the second record.
Q. What happens when the IP addresses change?
A. We will advise you that your IP addresses should be changed in the Settings -> Domain tab. Your custom domain will continue to function indefinitely, but no new signups will be allowed on the old IP addresses.
Q. Why did it take until now to get this feature?
A. This is a new feature for both Cloudflare and Bubble. When we told Cloudflare about our customers’ difficulties with the CNAME setup, they told us about this feature (which was still in beta at the time). We have been working with them since December to make this the best feature we can.
If you are using Cloudflare for DNS and you get 1014 errors on your custom domain, go into your DNS settings and set your custom domain to DNS only (“grey cloud”)
If you change your DNS records from
app.bubble.ioto our IPs and you get a 1000 error, go into your Bubble app, delete your custom domain, and re-create it exactly as it was. Within a few minutes the 1000 errors should clear up.