Website URL
Error Message
Other Information
What happened to CNAME verification? I know the qzz.io NS is f****d, but using CNAME always worked out through Cloudflare…
Yes, I made some changes to the domain verification flow. Specifically, if the client area detects problems with your domain name that should prevent you from completing the verification challenges, it won’t even give you the option to do so. It’s intended to be helpful, so you don’t waste your time trying to complete DNS challenges that cannot possibly be completed.
But I did not consider cases like qzz.io where the nameservers are absolutely not working as they should, but are functional enough that you could host a website on it.
I’m not sure what to do with this. I understand that you want to host your domain here, but I don’t really want to start building loopholes around checks like these because it creates more options that could cause more confusion if people ignore these warnings when their domain is really not working.
For now, you can add the domain through the control panel instead. It doesn’t have these additional checks so you can add the domain there. I’m only telling you this for qzz.io domains, if there are other cases where domains are incorrectly being blocked, I want to know so I can review the checks.
But I also want to suggest that you maybe try to reach out to qzz.io about this so they can fix their nameservers, or consider using a subdomain from a provider that has nameservers that work better.
Welp, had I known about this change before I started moving my domain, I would have just kept it on Jri Family 1. The client area was better with adding my domain, the control panel doesn’t seem to pick up the CNAME record the way the client area did.
Preflight verification is annoying. I get why it’s used, but still…
I’ve already reached out to qzz.io’s provider…
The UX in the client area is definitely better in my (very biased) opinion, but ultimately, the client area just uses the same endpoints in the control panel to actually add the domain. So if you could add it through the client area, you can also add it through the control panel.
If that’s the case, then why does the control panel never seem to pick up on the CNAME record, and the client area’s older Add Domain did? Now that’s just confusing…
It uses the same endpoint to add the domain, but not to check if the domain is availble. I think that there doesn’t exist an endpoint for this in the first place…
So the Client Area uses independent checks.
And even with that the statement is still true: if you can add it with the Client Area you can add it with the Control Panel. Client Area displaying a green checkmark for the CNAME is not adding it.
If I had to guess, I’d say that either you didn’t setup the correct CNAME record, or the broken qzz.io nameservers are causing intermittent issues with the checks and you just got lucky in the past.
The client area talks to the control panel to add the domain. If the control panel doesn’t accept the domain, you cannot add it through the client area either. The client area does extra checks, but those are mostly informational.