Domain moved, but everything is working

Application Performance DNS & Network
1

What is the name of the domain?

podcastbooks.club

What is the issue you’re encountering

I received an email saying my domain is moved and would be deleted if I don’t do something

What steps have you taken to resolve the issue?

dns and nameservers continue to confuse the ■■■■ out of me. Right now my app is hosted at digital ocean, but I’m using cloudflare for static image hosting. I tried using the custom domain at some point so my image urls would be domain.com/images/… but settled for now for using the pub…r2.dev/… route for testing.

I think the email is referring only to the screenshot below and not the r2 bucket or object or however it’s called, but I’d rather not wait around to find out.

What feature, service or problem is this related to?

DNS records

Screenshot of the error

cloudflarescreenshot.png

2 
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

is currently the name servers in the parent registry for that domain.

That is correct.

As the name severs has been changed to DigitalOcean, you have technically moved your domain name away from Cloudflare.

At some time in the future, the Cloudflare configuration will be automatically purged, if you do not change them back before then.

3

Does that mean that the URL won’t be publicly accessible as it is now after cloudflare shuts that down? All I really care about is that the static images will continue to be accessible for now. I tried doing the custom domain stuff, but this will be in development and what’s accessible online is essentially just the a test version.

Does that make sense? TLDR will i expect podcastbooks.club to go away in a few days or is this just about the custom domain shenanigans that I didn’t actually need…at least not yet?

4

If that requires the inclusion of Cloudflare directly, then you will need to change the name servers back to Cloudflare, in order to keep the operations you have directly with Cloudflare intact.

However, …

Looking further at your domain name, and the HTTP requests when pointing my browser to your website, I see headers such as “x-do-app-origin” and “x-do-orig-status”, which COULD indicate that you’re using DigitalOcean’s App Platform, to serve your website.

If that is the case, then the best course of action for you, will be to reach out to DigitalOcean, and ask them whether your set up with them seems to be correct for their platform, … or not.

DigitalOcean may be fronting their App Platform with Cloudflare, so that traffic to your website (while using the App Platform) is going through Cloudflare, and such kind of set ups, where you’re onboarding your website through a third party’s SaaS system, may be possible even without using Cloudflare directly (as well as the Cloudflare name severs).

DigitalOcean will however be the only party, which can provide assistance to you, while you’re using their platform.

5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.