In the following, we consider the issued record as follows
・Certificate validation TXT name _acme-challenge.example.ne.jp
・Certificate validation TXT value proof_old_value
However, after the customer added the TXT record, the Certificate validation TXT value was changed.
This was confirmed by the Cloudflare GUI and dig command that the value had changed.
Therefore, the Certificate status in Custom Hostnames has not changed from Pending Validation(TXT).
・Certificate validation TXT name _acme-challenge.example.ne.jp
・Certificate validation TXT value proof_new_value
This occurred not once, but twice.
When we verified internally with our DNS previously, the Certificate validation TXT was changed once, but only once, and then the Certificate status became Active.
What is the cause of this problem and what is the solution?
I think the possible reasons are as follows, but I would like to know if there is any discrepancy.
・TTL problem with the client’s DNS.
・Internal problem with Let’s Encrypt
We have already sent you a support request.
The ticket number is 2768579.
The title is also the same. After setting Custom Hostnames and the client sets the Certificate validation TXT value in DNS, the Certificate validation TXT value is changed.
This ticket was submitted on 4/20, but no official response has been received yet.
I escalated this post for the attention of the Customer Support Team so they can get back to you here. I shared your ticket number so that they can track it.
Ah, was wondering where this ticket/post went off to.
The ticket closed after some time due to non response from the Customer.
But the issue was, the Customer was using the Cloudflare for SaaS product.
The Custom Hostname cert offered was from Google.
The hostname issued to did not have Google CA configured, resulting in a bit of validation mess.
The solution is to have Google CA added to the domain where the hostname is issued to.