Point the root at Render’s load balancer — an ALIAS or flattened CNAME to your-service.onrender.com, or an A record to 216.24.57.1 — and www with a CNAME to the same onrender.com name. Render serves IPv4 only, so remove AAAA records.
The records to add
| Name | Type | Value |
|---|---|---|
@ | ALIAS / ANAME, or A | your-service.onrender.com, or 216.24.57.1 |
www | CNAME | your-service.onrender.com |
On Cloudflare, use a CNAME (flattened) at the root rather than the A record, as Render advises. Adding one of the root or www in Render adds the other with a redirect.
| IPv6 | Not supported — remove AAAA records |
| Certificate | Let’s Encrypt or Google Trust Services |
Check your domain
Enter your domain: we look up its records and compare them with what Render expects — the root, www, and any record left over from before.
Step by step
- In the service’s settings, add the custom domain.
- At your DNS host, point the root at the service (ALIAS) or at 216.24.57.1, and add the www CNAME.
- Remove AAAA records and any forwarding records your registrar added.
- Click Verify in Render, then wait for the certificate.
What to remove
- AAAA records — Render uses IPv4.
- Extra values such as a registrar’s forwarding records.
The certificate
Render issues certificates from Let’s Encrypt and Google Trust Services; CAA records must allow letsencrypt.org and pki.goog. Behind Cloudflare, keep the record DNS only until the certificate is issued, then proxy it if you like, with SSL mode Full.
Common mistakes
- An A record at the root on Cloudflare instead of a CNAME.
- Leaving AAAA records.
- A 502 just after verifying is normal while routing updates.
Sources
Records checked on 26 September 2026 against these official sources:
- Custom Domains on Render — render.com
- Configuring DNS Providers — render.com
- Configuring Cloudflare DNS — render.com
- Fully Managed TLS Certificates — render.com