Hi ddapson, I also noticed that the certificate in the CNAME record “value” expired in under 12 hours rather than the 72 hours documented so once I fixed the CNAME record the verify still failed for me too. To fix that, I hit the button to start over and generated new CNAME record values, then I updated DNS again and the validation ran OK. There is a catch-22 in this because if the certificate goes away in under 12 hours but the CNAME record change can take up to 24 hours to propagate you may never be able to successfully validate. As much as I dislike GoDaddy, the DNS record change was available within an hour for me.
It’s also worth mentioning that when I regenerated the CNAME record, the value may not have changed but I didn’t keep the old value to compare so I’m going by memory and could be wrong. If that’s the case hitting the button to start over may have just recreated the certificate for another 12 hours in which case the catch-22 doesn’t exist and the existing CNAME change would still be OK and you could validate immediately after hitting the button to start over. I hope that helps, it was very frustrating trying to get that working.
