Cannot change the target of CNAME record

Website, Application, Performance DNS & Network
1

Hello!
I have the proxying CNAME record that has been migrated from other Cloudflare account.
I trying to change the target to the new, but it changes only in the dashboard, the CNAME record still lead to the old target, even after several days.
I’ve tried to delete and recreate a record, but it didn’t help.

The new record with a different name works and changes without problems.

What should I do to fix it?

Thanks in advance for your help.

3

Can you show a screenshot of the DNS records, or give the CNAME, domain and what the target was, and now should be.

1 Like
4

Снимок экрана 2024-03-25 в 21.00.29
Снимок экрана 2024-03-25 в 21.00.292814×192 29.5 KB

Two CNAME records.
The first storage2 works ok and leads to dyorstorage.ams3.digitaloceanspaces.com.
The second storage leads to old dyor-storage.fra1.digitaloceanspaces.com

5

What is the domain name?

6

Sorry)

storage.dyor.io

7

Can you try setting the two CNAMEs to “DNS only” instead of “Proxied”.

8

Done and there’re no changes yet.

How many time need to apply changes?

9

The CNAMEs can be seen to be resolving ok…

dig +short storage.dyor.io
dyorstorage.ams3.cdn.digitaloceanspaces.com.
104.18.42.227
172.64.145.29

dig +short storage2.dyor.io
dyorstorage.ams3.cdn.digitaloceanspaces.com.
104.18.42.227
172.64.145.29

The IP addresses are still for Cloudflare, Digital Ocean does use Cloudflare for some of their services so that’s expected.

The responses still show fra/ams so you may need to check with Digital Ocean.

curl https://storage.dyor.io
<?xml version="1.0" encoding="UTF-8"?><Error><Code>AccessDenied</Code><Message></Message><BucketName>dyor-storage</BucketName><RequestId>tx00000746faca0cda00937-006601d236-e71a9ec6-fra1b</RequestId><HostId>e71a9ec6-fra1b-fra1-zg02</HostId></Error>

curl https://storage2.dyor.io
<?xml version="1.0" encoding="UTF-8"?><Error><Code>AccessDenied</Code><Message></Message><BucketName>dyorstorage</BucketName><RequestId>tx000005d3acde98a5f6838-006601d23a-53d083e0-ams3c</RequestId><HostId>53d083e0-ams3c-ams3-zg03</HostId></Error>
2 Likes
10

Thank you!
Now I trying to solve the problem with Digital Ocean.

11

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