# "Issue with your domain name" error message

**URL:** <https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501>\
**Category:** Need help\
**Created:** [July 26, 2023, 11:50pm UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501 "2023-07-26T23:50:02Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![william4](https://avatars.discourse-cdn.com/v4/letter/w/f475e1/32.png) [@william4](https://forum.bubble.io/u/william4)\
**Post date:** [July 26, 2023, 11:50pm UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/1 "2023-07-26T23:50:02Z")

</div>

Hi everyone,  
Today I was working on a small feature within my app, and suddenly when I tried to preview it the following message appeared:

 ![image](https://us1.discourse-cdn.com/bubble/original/3X/4/6/4603ed0a645e4714a0ce9f5e513e11e414f1a751.png)

There has not been any DNS changes. Does anyone know what could be the cause for this error appearing so randomly?

---

<div class="post-metadata">

**Author:** ![SJL](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/sjl/32/93757_2.png) [@SJL](https://forum.bubble.io/u/SJL)\
**Post date:** [July 27, 2023, 12:04am UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/2 "2023-07-27T00:04:28Z")

</div>

I just saw that as well. My guess is that there was a minor update to Bubble, and the message has been shown erroneously.

Especially if you, I and anyone else got it without changing anything.

I was worried for a second that my domain name had expired, but the fact you got the message as well means I can comfortably ignore it.

---

<div class="post-metadata">

**Author:** ![gabriel.guilhem](https://avatars.discourse-cdn.com/v4/letter/g/df788c/32.png) [@gabriel.guilhem](https://forum.bubble.io/u/gabriel.guilhem)\
**Post date:** [July 27, 2023, 12:08am UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/3 "2023-07-27T00:08:41Z")

</div>

I just saw it too.

I noticed that the A records I had in Cloudflare were different than the ones Bubble was showing me.

When I replaced the IPs, my app got out of service - even though the DNS was already propagated. I switched it back to the original IPs and it looks everything is fine now again - the Bubble error message is still there.

I think it’s a bug.

---

<div class="post-metadata">

**Author:** ![william4](https://avatars.discourse-cdn.com/v4/letter/w/f475e1/32.png) [@william4](https://forum.bubble.io/u/william4)\
**Post date:** [July 27, 2023, 12:13am UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/4 "2023-07-27T00:13:46Z")

</div>

Thank you @SJL and @gabriel.guilhem. As both of you suggest if this is something appearing without any real cause, it might as well be a bug.

---

<div class="post-metadata">

**Author:** ![wesfrank](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/wesfrank/32/79725_2.png) [@wesfrank](https://forum.bubble.io/u/wesfrank)\
**Post date:** [July 27, 2023, 12:33am UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/5 "2023-07-27T00:33:10Z")

</div>

I’m having this issue too. My website is currently down using the new DNS records.

---

<div class="post-metadata">

**Author:** ![andrew](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/andrew/32/3404_2.png) [@andrew](https://forum.bubble.io/u/andrew)\
**Post date:** [July 27, 2023, 2:15am UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/6 "2023-07-27T02:15:21Z")

</div>

Same, changing the dns caused cloudflare 1000 error, reverting to previous works, but with this error popping up

---

<div class="post-metadata">

**Author:** ![cm1](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/cm1/32/3947_2.png) [@cm1](https://forum.bubble.io/u/cm1)\
**Post date:** [July 27, 2023, 6:41am UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/7 "2023-07-27T06:41:40Z")

</div>

same issue here. what should we do?

---

<div class="post-metadata">

**Author:** ![bart](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/bart/32/169086_2.png) [@bart](https://forum.bubble.io/u/bart)\
**Post date:** [July 27, 2023, 7:34am UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/8 "2023-07-27T07:34:15Z")

</div>

Same here

---

<div class="post-metadata">

**Author:** ![NoCodePhill](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/nocodephill/32/231606_2.png) [@NoCodePhill](https://forum.bubble.io/u/NoCodePhill)\
**Post date:** [July 27, 2023, 10:34am UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/10 "2023-07-27T10:34:11Z")

</div>

Getting the same issue across several apps, unusable at the moment.

---

<div class="post-metadata">

**Author:** ![tart2000design](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/tart2000design/32/171697_2.png) [@tart2000design](https://forum.bubble.io/u/tart2000design)\
**Post date:** [July 27, 2023, 1:26pm UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/11 "2023-07-27T13:26:59Z")

</div>

Same problem here! Everything was working fine and now my settings page is telling me I haven’t got SSL anymore and that my app has ‘bad DNS records’… 😱  
Any idea on how to fix that??

---

<div class="post-metadata">

**Author:** ![mikeloc](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/mikeloc/32/93001_2.png) [@mikeloc](https://forum.bubble.io/u/mikeloc)\
**Post date:** [July 27, 2023, 1:51pm UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/13 "2023-07-27T13:51:27Z")

</div>

You should all submit [bug reports](https://bubble.io/support/report), if you haven’t done so already.

---

<div class="post-metadata">

**Author:** ![jacob13](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@jacob13](https://forum.bubble.io/u/jacob13)\
**Post date:** [July 27, 2023, 3:17pm UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/14 "2023-07-27T15:17:42Z")

</div>

Seeing this on my end as well.

---

<div class="post-metadata">

**Author:** ![tart2000design](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/tart2000design/32/171697_2.png) [@tart2000design](https://forum.bubble.io/u/tart2000design)\
**Post date:** [July 27, 2023, 8:51pm UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/15 "2023-07-27T20:51:11Z")

</div>

Bubble support advises to **not** change your DNS settings to the ones recommended in the ‘domain settings’ tab… It seems they’re working on it.

---

<div class="post-metadata">

**Author:** ![hankenb](https://avatars.discourse-cdn.com/v4/letter/h/49beb7/32.png) [@hankenb](https://forum.bubble.io/u/hankenb)\
**Post date:** [July 27, 2023, 10:10pm UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/16 "2023-07-27T22:10:53Z")

</div>

Thanks. I was literally just about to do that 😁 .

---

<div class="post-metadata">

**Author:** ![SJL](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/sjl/32/93757_2.png) [@SJL](https://forum.bubble.io/u/SJL)\
**Post date:** [July 27, 2023, 10:36pm UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/17 "2023-07-27T22:36:42Z")

</div>

I would say by reading everyone’s posts **DO NOT CHANGE ANYTHING** based on the message.

The message is an error, your existing settings are fine.

The only people who seem to have had issues are those who proceeded to change records based on the message.

---

<div class="post-metadata">

**Author:** ![NoCodePhill](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/nocodephill/32/231606_2.png) [@NoCodePhill](https://forum.bubble.io/u/NoCodePhill)\
**Post date:** [July 28, 2023, 1:47pm UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/18 "2023-07-28T13:47:13Z")

</div>

Changed nothing (i,e sit and wait for Bubble to resolve).

This morning it had gone away, so thought all was well.

Now its back again.

---

<div class="post-metadata">

**Author:** ![dan8](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/dan8/32/33110_2.png) [@dan8](https://forum.bubble.io/u/dan8)\
**Post date:** [July 29, 2023, 6:39am UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/19 "2023-07-29T06:39:57Z")

</div>

Can confirm this also. I was connecting a project to a domain but the IPs provided result in DNS resolve issue (cloudflare page). The project was using standard bubble domain but had a custom domain a few months back. Support said they are aware and it’s been almost 48 hours to date.

---

<div class="post-metadata">

**Author:** ![hankenb](https://avatars.discourse-cdn.com/v4/letter/h/49beb7/32.png) [@hankenb](https://forum.bubble.io/u/hankenb)\
**Post date:** [July 29, 2023, 1:48pm UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/20 "2023-07-29T13:48:41Z")

</div>

The DNS error went away for me. Everything seems to be working correctly now (at least for me).

---

<div class="post-metadata">

**Author:** ![georgecollier](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/georgecollier/32/182327_2.png) [@georgecollier](https://forum.bubble.io/u/georgecollier)\
**Post date:** [July 30, 2023, 10:47am UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/21 "2023-07-30T10:47:55Z")

</div>

@dan8 you still getting Error 1001 for the new domain connection? It’s frustrating it’s been a few days and still not fixed…

 ![image](https://us1.discourse-cdn.com/bubble/original/3X/c/2/c2422215e51f4d25553e5d1d0e19de635e9613e8.jpeg)

---

<div class="post-metadata">

**Author:** ![dan8](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/dan8/32/33110_2.png) [@dan8](https://forum.bubble.io/u/dan8)\
**Post date:** [July 30, 2023, 5:24pm UTC](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501/22 "2023-07-30T17:24:46Z")

</div>

Not anymore. I was advised to use an older IP range which my project was previously connected to. After using this for the A records, it started working again. So, if you had previous IP records assigned, use those.

[Next page](https://forum.bubble.io/t/issue-with-your-domain-name-error-message/274501.md?page=2)
