DNS setup: A records, CNAME and the apex

Subdomains: CNAME

For any subdomain (www, app, api, shop…) add a CNAME to our edge hostname. This is the simplest option and works at every DNS provider.

CNAME   www   edge.georevers.com.

Root / apex domain: A records

DNS forbids a CNAME at the zone apex (example.com with no subdomain). Use A records pointing at our stable entry IPs instead. These IPs are anycast-style and don't change — we move edges and rotate banned addresses behind them, so you set this once.

A    @    <entry-ip-1>
A    @    <entry-ip-2>

If your DNS provider supports CNAME flattening or ALIAS at the apex (Cloudflare, Route 53, and many others do), you can point the apex at edge.georevers.com instead and skip the A records.

Keep your DNS provider

You do not delegate your domain to us and you do not change nameservers. Everything else in your zone (MX, TXT, other subdomains) stays exactly as it is.

TLS

Once DNS resolves to us we issue a free, auto-renewing Let's Encrypt certificate for the hostname. Bring-your-own-cert is available on Business and Enterprise. There is nothing to upload for the default flow.

Verification

After the record propagates, the dashboard marks the site Active. If it stays pending, double-check that the record points at the exact value we show and that no conflicting record (old A/AAAA, proxied/orange-cloud) is shadowing it.