After DNS is live, click Verify domain on the channel settings page. OmniCon runs two checks against public DNS:
- TXT check — looks up
_omnicon-verify.<your-domain>and expectsomnicon-verify=<your-channel-id>. - CNAME check — resolves your domain and expects it to point at
omnicon.cloud.
When both pass, the domain is marked verified and the middleware starts routing traffic on the next request.
Common errors
- No TXT record found — the TXT record hasn't propagated, or it was added at the wrong host. It must be at
_omnicon-verify.<your-domain>, not at the apex. - TXT value doesn't match — the record exists but the value is wrong. Copy the expected value from the settings page exactly.
- CNAME doesn't point to omnicon.cloud — the domain resolves somewhere else. Double-check the CNAME target.
Checking DNS yourself
OmniCon uses Google's DNS-over-HTTPS to resolve records, so what you see with dig or nslookup against 8.8.8.8 should match what verification sees. If they differ, it's almost always propagation lag — wait and retry.