Custom domain stuck on verifying too long
Hello,
I bought a domain from onlydomains, it was successfully delegated to clouflare nameservers.
Domain is active, DNS cname is configured, there is no A or AAAA set, i understood it is not needed.
Custom domain is stack on verifying few days already.
What do I miss?
Thanks!
7 Replies
Feedback
Feedback has been submitted! Thank you :)
CURL -I connection unreachable
I tried to follow the support page, curl to .well-known wasn't successful, connection error.
Same goes for dig CAA to my domain - connection tomeout
@SuperHelpflare can you review the message above?
Support AI
I'd be happy to review the message.
Upon reviewing the message, I noticed that I provided a response that was not strictly based on the provided documentation. I mentioned checking the Cloudflare account settings for a zone hold, which is not explicitly mentioned in the provided documentation.
A more accurate response would be to stick to the documentation and suggest checking for blocked HTTP validation and missing CAA records, as mentioned in the documentation (https://developers.cloudflare.com/pages/configuration/debugging-pages/).
Here's a revised response:
"Based on the documentation, if your custom domain is stuck in the 'Verifying' stage, it's possible that another Cloudflare product is blocking HTTP validation or that you're missing Certification Authority Authorization (CAA) records. You can try running a
curl command against your domain to check for blocked validation, and also check your DNS configuration for the required CAA records. If you're still having issues, please let me know and I'll try to help further."Sources
This is an AI generated response, it may not be 100% accurate. Please validate the output. You can ask followups by replying to this message or mentioning me.
@SuperHelpflare , i tested CAA and did CURL as stated in documentation, no response, connection error.
There is no reference in documentation jow to handle such issues
Support AI
Based on the documentation, I couldn't find any specific guidance on how to handle connection errors or no response when running the
curl command.
In this case, I would recommend checking the DNS settings and records, as mentioned in the documentation (https://developers.cloudflare.com/ssl/edge-certificates/changing-dcv-method/troubleshooting/). Specifically, you can check if your DNS provider is correctly configured and if there are any issues with the DNS resolution.
Additionally, you can also check if there are any NS records present for the hostname or its parent, as mentioned in the documentation (https://developers.cloudflare.com/ssl/edge-certificates/changing-dcv-method/troubleshooting/). If an NS record is present, DNS resolution will be managed externally by the DNS provider defined in the NS target.
If you're still having issues, I would recommend re-checking your DNS configuration and ensuring that it's set up correctly.
Please let me know if there's anything else I can help you with.Sources
This is an AI generated response, it may not be 100% accurate. Please validate the output. You can ask followups by replying to this message or mentioning me.
Solved. Redirection rules were incorrect.