Custom domain (CNAME) verification fix

We've released a fix for the custom domain verification process (CNAME).

Previously, some users experienced issues where their CNAME records were correctly configured but failed to verify, due to DNS propagation delays or verification timing. DNS is genuinely eventually-consistent — records take time to propagate — but the verifier wasn't patient or transparent enough about that, so "configured correctly, verified never" was a state you could get stuck in with no explanation.

What's new:

• Improved domain verification reliability — correct records now verify, even when propagation is slow.
• Better retry mechanism for pending DNS updates, so a record that isn't visible yet gets rechecked instead of failed.
• Clearer feedback and status messages when connecting your domain, so you can tell "still propagating" from "actually misconfigured."

You can now connect and verify custom domains faster and with fewer interruptions. A branded portal domain is one of those touches that makes a program feel like yours rather than a third-party tool — the path to it shouldn't require DNS archaeology, and now it doesn't.

If a domain of yours previously refused to verify despite correct records, re-running verification should now succeed.