Every app, website and bucket gets a generated address that works straight away. To use your own domain you either add a CNAME record at your current DNS provider, or move the whole domain's DNS to RandallFlare.
1Open the app (or website, or bucket) in the console and add the hostname under Domains, or run rr domains add www.example.com.
2Create the two CNAME records the console shows at your DNS provider: one from your hostname to the edge, and one for _acme-challenge.<hostname> that lets us issue its certificate.
3Wait for the status to turn green. The HTTPS certificate is issued within a few minutes and renewed automatically.
An apex domain such as example.com cannot be a CNAME at most providers. Use a www subdomain, a provider that supports CNAME flattening, or option 2.
Once the registrar has switched, you manage every record (A, AAAA, CNAME, MX, TXT, SRV and more) in the console or with rr dns record add. Records that point at your RandallFlare products are created for you, apex domains included, and DNS over HTTPS can be switched on for the zone.
When you add a custom domain, the console shows the CNAME target for that resource: <id>.compute.randallflare.com for apps and sites, <id>.cdn.randallflare.com for CDN websites, <id>.r2.randallflare.com for buckets. The target is permanent for the resource, so your record keeps working as the platform's nodes change. It is only a target: it does not open anything by itself — your domain and the generated address do.
Turn on Log queries on a hosted zone and every question the edge answers for it is recorded with the resolver IP and the EDNS client subnet. Read them for ten minutes per name at GET /api/edge/v1/dns/<zone>/queries?name=<name>, with an owner token or the zone's read-only key in X-Dns-Log-Key (shown on the zone page; it can read nothing else). A complete leak test app is in Recipes.