DNS Configuration
To use a custom domain with UrlEdge, follow the DNS wizard in the console. New domain setups use TXT ownership verification plus a CNAME-style traffic record that points to the selected UrlEdge node.
Custom domains (CNAME)
For subdomains such as go.brand.example or links.brand.example, add the CNAME shown in the wizard. The target changes with the selected edge node, so copy the exact value from the console instead of reusing an old docs example.
| Type | Host / Name | Value / Target | TTL |
|---|---|---|---|
| CNAME | go | edge.urledge.online | Auto / 3600 |
Cloudflare Users: Ensure the "Proxy status" cloud icon is set to Grey (DNS Only). If it is Orange (Proxied), UrlEdge cannot verify SSL certificates automatically.
Root domains and edge nodes
New setups are CNAME-first. If you need an apex domain such as brand.example, use your DNS provider’s CNAME Flattening, ALIAS, or ANAME feature and point it to the same target from the wizard. If your provider only supports plain A or AAAA records at the apex, use a subdomain or move DNS to a provider with flattening support. Legacy A-record domains can still be re-verified, but do not start new setups from old Anycast IP examples.
CNAME targets you may see in the wizard:
Common Issues
Verification Pending?
DNS propagation can take time. If it's been over 1 hour, check for conflicting CNAME, A, or AAAA records on the same host. Remove old origin, CDN, or redirect-service records before verifying again.
SSL Error?
We provision SSL through Cloudflare for SaaS. If issuance stays pending for an extended period, check that your CNAME or flattened target points to the UrlEdge node shown in the wizard, and confirm the Custom Hostname status in Cloudflare has moved beyond pending.