Regarding Cname resolution issues in DNS

I have been using a special CNAME parsing value for a long time, but recently I found that it could not be parsed successfully. What is the reason?
For example:
name:_910bec6296b54544faa535036da1

content:_da0d69362b3897343aa4.bvddyb.acm-validations.aws.

Welcome to the Cloudflare Community. :logodrop:

Without your domain name the Community cannot lookup your CNAME.

If you switched it from :grey: to :orange:, the name will be published as A and AAAA records. If you need it to appear as a CNAME, it must be :grey: .

1 Like
my domain is caverean.com,can u help me check it?

I see no records (CNAME or other) returned by queries for the name _910bec6296b54544faa535036da1.caverean.com

Can you provide a screenshot of your Cloudflare DNS that shows that record exists?

Name:_43cfb661513a3f0f4665fec3f32dd210
Value:_2828a476721f4e10267019997ad4ffe3.lwsvfpkkct.acmvalidations.aws.
This name&value never takes effect, but others can

That CNAME shows up for me.

1 Like

can you plz be more specific?

Not really, but you can look for yourself:

Dig (DNS lookup)

you mean this cname hasn’t taken effect yet?

It’s working fine.

The name you’re pointing it to, _2828a476721f4e10267019997ad4ffe3.lwsvfpkkct.acmvalidations.aws, doesn’t exist. You’ll want to change that so it ends with acm-validations.aws (with the hyphen).

1 Like

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