## Custom domain stuck on “Verification record was not found” despite correct CNAME (weeks later)
**Tenant region:** US
**Custom domain:** `login.ctrak.ca`
**Certificate type:** Auth0-managed
### Issue
I added a custom domain in Branding > Custom Domains and set up the CNAME exactly as instructed, but verification has never succeeded. The dashboard alternates between showing:
- `PENDING VERIFICATION` with the banner: *“Error with domain login.ctrak.ca. The verification record was not found. You might need to wait a few minutes before we can discover it.”*
- `FAILED: INVALID CNAME`
This has been in place since **July 28** — so it’s well past any normal propagation window, not a “wait a few minutes” situation.
### What Auth0’s dashboard says to configure
- CNAME record name: `login.ctrak.ca`
- CNAME target: `dev-xxxxxxxxxxxx-cd-k1vwosv3wvnqt1au.edge.tenants.us.auth0.com`
### What’s actually in DNS
Verified in the Cloudflare dashboard for the `ctrak.ca` zone:
| Name | Type | Target | Proxy status |
| `login.ctrak.ca` | CNAME | `dev-xxxxxxxxxxxx-cd-k1vwosv3wvnqt1au.edge.tenants.us.auth0.com` | DNS only (grey-clouded, not proxied) |
The record matches the target Auth0’s dashboard asked for exactly, and it’s DNS-only (not proxied through Cloudflare), which I understand is required for Auth0-managed certs. I also ran `dig login.ctrak.ca -t CNAME +short` (the exact command the dashboard suggests) and it resolves correctly to the same target.
### Question
Since the DNS side checks out and has been stable for weeks, is this a known issue with Auth0’s verification/discovery step, or is there something else I should check on my end? Also open to hearing if there’s a way to force a re-check without deleting and recreating the custom domain (don’t want to lose the current state if support can see something from their side).
Happy to share the full tenant name via DM if that helps a responder look it up.