DNS Issue - A Record Not Pointing Correctly to Bubble Server

Hello,

I am experiencing an issue with my domain setup for justbu.me. The following error message continues to appear even after DNS adjustments:

“We found bad DNS records for justbu.me. These records are pointing to the servers that do not belong to Bubble: A record 52.9.166.110, A record 50.18.215.94. It can take up to 24 hours for domain records to propagate across the internet, so if you think it is set up correctly, please try again in a bit. If you are using HTTPS for this site, the validation can take 24-36 hours to complete.”

Steps I have taken so far:

  1. Removed the A records pointing to 52.9.166.110 and 50.18.215.94 from Netlify.

  2. Checked DNS propagation using DNSChecker, and all A records are now pointing to the correct Bubble IP addresses.

  3. Waited over 36 hours for DNS changes to propagate fully.

However, the error message still persists. Could you please provide guidance on the next steps to resolve this issue?

Thank you.

Hi @seoulization,

According to MX Toolbox it looks like the DNS records are pointed correctly. Can you try clicking the “Check my settings” button in the editor under Domains/Email?

I am currently experiencing issues using Cloudflare Workers to implement a reverse proxy for my domains sagyo.me and seoulization.com, both of which should route traffic to my Bubble application hosted at justbu.me.

Here is a summary of the situation and previous steps taken:

  1. Configuration Details:

sagyo.me and seoulization.com are configured on Cloudflare to route through Workers to justbu.me.

• The SSL/TLS setting on sagyo.me is set to “Flexible,” while justbu.me follows Bubble’s default SSL configuration.

• Despite multiple verifications of DNS, SSL, and firewall settings, accessing sagyo.me or seoulization.com results in a 522 Error (“Connection Timed Out”), indicating connectivity issues between Cloudflare and the Bubble server.

  1. Previous Interaction with Support:

• I initially followed Bubble’s video tutorial for domain configuration and consulted with Bubble Support regarding DNS records. At the time, the error identified was related to incorrect DNS records pointing to external servers. This issue has since been corrected.

• Netlify was previously managing the DNS records for justbu.me, but I have now reverted management to the original domain provider to avoid any potential conflicts.

  1. Current Status and Request:

• I would like to understand if there are any specific settings or configurations within Bubble that might conflict with a reverse proxy setup using Cloudflare Workers.

• Additionally, if Bubble has recommended best practices for implementing reverse proxies with Cloudflare Workers, I would appreciate any guidance or documentation on this matter.

Thank you very much for your assistance and any insights you can provide to help resolve this connectivity issue.

hey - I had a similar problem - not solved by fixing but used a workaround

under lobby4.app / GoDaddy - app works bad! super laggy and buggy

under lobby4.pro / Hostinger - works flawless!

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