GoDaddy Setup Bug: Works for example.com, but not www.example.com

Hello Bubble Community,

I’m experiencing a strange problem with my domain setup and I’m hoping someone can shed some light on it. Here’s what’s happening:

  1. I’ve connected my GoDaddy domain to Bubble, and it works perfectly for the naked domain (e.g., artishow.co) (see screenshot below).

  1. However, when I try to access the site using ‘www’ (e.g., www.artishow.co), it redirects me to a page with a CloudFlare error (see screenshot below).

I’ve tried different DNS configurations, including the following (my current one is configuration 1):

- Configuration 1:

SOA Record
    @	3600	 IN 	SOA	ns49.domaincontrol.com.	dns.jomax.net. (
    					2023102610
    					28800
    					7200
    					604800
    					3600
    					) 

A Record
    @	600	 IN 	A	104.16.36.105
    @	600	 IN 	A	104.16.42.105
    @	600	 IN 	A	104.19.240.93
    @	600	 IN 	A	104.19.241.93
    www	600	 IN 	A	104.16.36.105
    www	600	 IN 	A	104.16.42.105
    www	600	 IN 	A	104.19.240.93
    www	600	 IN 	A	104.19.241.93

TXT Record
    @	3600	 IN 	TXT	"NETORGFT12688481.onmicrosoft.com"
    @	3600	 IN 	TXT	"v=spf1 include:secureserver.net -all"
    _dmarc	3600	 IN 	TXT	"v=DMARC1; p=quarantine; pct=90; sp=none"
    _webflow.www.about	3600	 IN 	TXT	"one-time-verification=4b6f24ab-66f3-4025-810b-c8375ac65e84"

CNAME Record
    about	3600	 IN 	CNAME	proxy-ssl.webflow.com.
    Autodiscover	3600	 IN 	CNAME	autodiscover.outlook.com.
    em2951	1800	 IN 	CNAME	u33625315.wl066.sendgrid.net.
    email	3600	 IN 	CNAME	email.secureserver.net.
    lyncdiscover	3600	 IN 	CNAME	webdir.online.lync.com.
    msoid	3600	 IN 	CNAME	clientconfig.microsoftonline-p.net.
    roadmap	3600	 IN 	CNAME	cname.prodcamp.com.
    s1._domainkey	1800	 IN 	CNAME	s1.domainkey.u33625315.wl066.sendgrid.net.
    s2._domainkey	1800	 IN 	CNAME	s2.domainkey.u33625315.wl066.sendgrid.net.
    sip	3600	 IN 	CNAME	sipdir.online.lync.com.
    trail	3600	 IN 	CNAME	custom.lemlist.com.
    www.about	3600	 IN 	CNAME	proxy-ssl.webflow.com.
    _domainconnect	3600	 IN 	CNAME	_domainconnect.gd.domaincontrol.com.

SRV Record
    _sip._tls.@	3600	 IN 	SRV	100	1	443	sipdir.online.lync.com.
    _sipfederationtls._tcp.@	3600	 IN 	SRV	100	1	5061	sipfed.online.lync.com.

NS Record
    @	3600	 IN 	NS	ns49.domaincontrol.com.
    @	3600	 IN 	NS	ns50.domaincontrol.com.

MX Record
    @	3600	 IN 	MX	0	artishow-co.mail.protection.outlook.com.

- Configuration 2:

SOA Record
    @	3600	 IN 	SOA	ns49.domaincontrol.com.	dns.jomax.net. (
    					2023102614
    					28800
    					7200
    					604800
    					3600
    					) 

A Record
    @	600	 IN 	A	104.16.36.105

TXT Record
    @	3600	 IN 	TXT	"NETORGFT12688481.onmicrosoft.com"
    @	3600	 IN 	TXT	"v=spf1 include:secureserver.net -all"
    _dmarc	3600	 IN 	TXT	"v=DMARC1; p=quarantine; pct=90; sp=none"
    _webflow.www.about	3600	 IN 	TXT	"one-time-verification=4b6f24ab-66f3-4025-810b-c8375ac65e84"

CNAME Record
    about	3600	 IN 	CNAME	proxy-ssl.webflow.com.
    Autodiscover	3600	 IN 	CNAME	autodiscover.outlook.com.
    em2951	1800	 IN 	CNAME	u33625315.wl066.sendgrid.net.
    email	3600	 IN 	CNAME	email.secureserver.net.
    lyncdiscover	3600	 IN 	CNAME	webdir.online.lync.com.
    msoid	3600	 IN 	CNAME	clientconfig.microsoftonline-p.net.
    roadmap	3600	 IN 	CNAME	cname.prodcamp.com.
    s1._domainkey	1800	 IN 	CNAME	s1.domainkey.u33625315.wl066.sendgrid.net.
    s2._domainkey	1800	 IN 	CNAME	s2.domainkey.u33625315.wl066.sendgrid.net.
    sip	3600	 IN 	CNAME	sipdir.online.lync.com.
    trail	3600	 IN 	CNAME	custom.lemlist.com.
    www	3600	 IN 	CNAME	@
    www.about	3600	 IN 	CNAME	proxy-ssl.webflow.com.
    _domainconnect	3600	 IN 	CNAME	_domainconnect.gd.domaincontrol.com.

SRV Record
    _sip._tls.@	3600	 IN 	SRV	100	1	443	sipdir.online.lync.com.
    _sipfederationtls._tcp.@	3600	 IN 	SRV	100	1	5061	sipfed.online.lync.com.

NS Record
    @	3600	 IN 	NS	ns49.domaincontrol.com.
    @	3600	 IN 	NS	ns50.domaincontrol.com.

MX Record
    @	3600	 IN 	MX	0	artishow-co.mail.protection.outlook.com.

I’ve also patiently waited 24 hours after each DNS change to ensure proper propagation. Despite these efforts, the problem persists.

I even contacted GoDaddy’s support and the second configuration is what they set up. They couldn’t identify the problem.

Has anyone encountered a similar problem or can provide guidance on how to configure my DNS settings to ensure that it works seamlessly with both the naked domain and ‘www’? Your insight would be greatly appreciated!

Thanks in advance.

Hello Bubblers!

I wanted to provide an update on the issue I was experiencing with my domain setup. Thanks to the help of the Bubble support team, who have been super responsive and helpful, the problem is now resolved.

It turns out that the issue was related to Cloudflare, which was blocking Bubble from resolving the issues on my domain. You can check the status of Cloudflare here.

Bubble’s technical support suggested that this behavior might be related to a CAA error on my top-level domain. As a solution, they recommended that I add certain CAA records to my top-level domain to ensure that it is assigned a new certificate and propagates correctly. The records they suggested are as follows:

0 issue "digicert.com; cansignhttpexchanges=yes"
0 issue "sectigo.com"
0 issue "letsencrypt.org"
0 issue "pki.goog; cansignhttpexchanges=yes"

You can see how to set this up in GoDaddy with this screenshot.


In their own words:

Bubble will periodically assign a new certificate to your application, and the list of certificates can change somewhat frequently. Adding these records should ensure that your domain is assigned a new certificate and thus propagates correctly.

I’ve already applied these CAA records as suggested, and after waiting more than a week, my site now works seamlessly with both the naked domain (e.g. artishow.co) and ‘www’ (e.g. www.artishow.co).

I’ve also asked for more details on what specifically solved the problem, and I’ll make sure to update this post once I receive that information.

Thanks to the Bubble support team for their help in resolving this issue. I hope this information is helpful to others who may be experiencing similar domain setup challenges.

UPDATE
There was nothing I could do. In their own words:

In this case, there was a larger issue going on with Cloudflare, so there is not anything that you can really do to prevent a similar case in the future. The only thing that could’ve been done at this point was reaching out to us so we can look directly into your specific domain and see what was going on, as well as wait for Cloudflare to resolve the issues on their end.

In general the best steps to take when setting up a domain are to follow the instructions we have here in our documentation, and then to wait 24 hours, but if there are still on going issues after that the best next step is to reach out to us.

This topic was automatically closed after 70 days. New replies are no longer allowed.