It appears you encountered an issue during authorization. In the message, authorizationAttemptInfo is showing failureReason____: CONFIG. This means that there was an issue with your DNS or load balancer configuration. This prevents the Managed Certificate from being issued.
It is best to review your DNS or load balancer configuration for your domain and try again. Please note that you will have to delete and create a new managed certificate resource to try again.
Please refer to the following troubleshooting pages below for more guidance:
A crucial part of troubleshooting this issue would be to verify if the dns record you created in your dns zone is publicly resolvable. Try to resolve it from your system (using nslookup or dig or host or ping) or online with one of the services like dnschecker and see if the name (_acme-challenge…) resolved to that long string ending in goog.
what is the value for that record? that’s what usually ends with “.goog.”
Go to dnschecker, edit the name of the record (copy the name of the record from Cloud DNS to avoid mistakes) and click Search to verify if the record is publicly resolvable.
In DNS checker, i see that the record is publicly resolvable.
and i am able to see that the certificate is active now as well.
But there is one thing that is eluding my understanding and that is in the following step why am i adding the CNAME record to the DNS zone in Cloud DNS. Shouldn’t i also add it to my records in Hostinger from whom i purchased the domain.