CNAME Sorry no record found!
CNAME Sorry no record found!
CNAMEs not resolving
Deleted all entries, and added them one by one.
Toggle between proxy and non proxy. Records are non-proxy at this time.
DNS records
Add CNAMEs
this is one of the CNAMEs:
CNAME
xopp5ubog56hiw2ugl2fep6ttgv7b7hw._domainkey xopp5ubog56hiw2ugl2fep6ttgv7b7hw.dkim.amazonses.com
DNS only
DKIM needs to be unproxied. If you kept switching back and forth without waiting too long, possible the proxied version was being cached for a while and not working.
You can see it exists here: DNS Propagation Checker - Global DNS Testing Tool
The example you gave was looking for a cname on your root, when you should be looking for a cname on xopp5ubog56hiw2ugl2fep6ttgv7b7hw._domainkey.rohetek.com
I haven’t changed the records for more than 12 hours. All records by A records are unproxied. DKIM should be unproxied
I am not sure I follow the second statement:
These are the records added but don’t see them resolving.
jqhwg6jydxyxhbrii3ecmugva2i4bfld._domainkey.rohetek.com
jqhwg6jydxyxhbrii3ecmugva2i4bfld.dkim.amazonses.com|
xopp5ubog56hiw2ugl2fep6ttgv7b7hw._domainkey.rohetek.com
xopp5ubog56hiw2ugl2fep6ttgv7b7hw.dkim.amazonses.com
tufvnmodyfonmpxyb3kap4c3lnlsiqvm._domainkey.rohetek.com
tufvnmodyfonmpxyb3kap4c3lnlsiqvm.dkim.amazonses.com
Oh, I see what you mean now and thank you for responding. Let me check the other CNAMES.
should root cname resolved if is not proxy?
I see all 3 of those
No, Root/Apex CNAMEs are not allowed per the DNS Specification, so Cloudflare flattens/resolves them down to just their A/AAAA records in order for them to function. CNAME flattening · Cloudflare DNS docs
Introducing CNAME Flattening: RFC-Compliant CNAMEs at a Domain's Root
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.