CNAME not verified by DNS checker

#1

Hi All,

I have a CNAME, which is actually working (as in the forward happens) but can’t be verified by using DNS checkers. The CNAME record is not “orange clouded”, the cloud is grey!

https://dnschecker.org/#CNAME/apta-student.coderacademy.edu.au

The problem I have with this is that I can’t use CNAME entries to verify domain ownership.

Any clue why? What I can do about it?

Thanks heaps!

#2

Do you have CNAME flattening (Flatten all CNAMEs) enabled at the bottom of your DNS page? This is an option on paid plans.

#3

Just noticed that this does work using an A record check… so it behaves as if it was “orange clouded”…

Not good for me - again, it doesn’t get accepted as ownership proof…

Still looking for answers…

Thanks!!

#4

It’s not :orange: behavior, because that would return a Cloudflare IP address. There’s also the unlikely chance you already have an A record for that hostname…unless, as I suggested above, you’re flattening the CNAME.

#5

Yes, cname flattening is on…

#6

That’s why. The verification process is looking for a typical CNAME response for what it’s aliasing to. If you disable “Flatten All CNAMEs”, that should fix it. Just set it for Flatten CNAME at root.

#7

Yes, that worked… Thanks heaps sdayman!

Why would I choose to use flatten all cmanes instead of flatten at root?

1 Like
#8

Flattening subdomain CNAMEs is handy for hiding the source of your subdomain. For example, your mail host. I have an MX record for mail.example.com, but “mail” is a CNAME to a third party mail host I’d rather not divulge. So I flatten that subdomain. It doesn’t completely hide the source, but it does provide a bit of whitelabeling.