CNAME type validation failed in some cases

[test_mail_new]

There is the problem that I found:

Someone want to apply the LetsEncrypt certificate for domain *.cre.com.hk.

Then he set a CNAME record for _acme-challenge.cre.com.hk and the value is example.com.

And example.com had set the right TXT value that LetsEncrypt expected.

I use dig cmd to check the TXT value of example.com. It worked and it's correct.

Then I dig _acme-challenge.cre.com.hk but the expected TXT value was not found.

Why ?

This is first time that I found CNAME type validation could be come up with this situation.

[JuergenAuer]

Hi @test_mail_new

@test_mail_new

Then he set a CNAME record for _acme-challenge.cre.com.hk

there is no CNAME. Not for _acme-challenge.cre.com.hk, not for (not relevant) cre.com.hk.

May be the name servers are buggy, that happens.

Or that user has done something wrong, but that's speculative.

[test_mail_new]

Yeah, he had remove the CNAME record.

Thank you for your opinion.

It seems that this case is rare.