DNS Setup for Render

Custom Domain DNS Setup for Render

Render is a cloud platform for hosting web services, static sites, and databases. Connecting a custom domain to a Render service requires configuring DNS records at your domain registrar or DNS provider to point to Render's infrastructure.

Configuring DNS for a Render Web Service

In the Render dashboard, open your service, click "Settings," and navigate to "Custom Domains." Add your domain — Render will display the DNS records you need to configure.

For a subdomain (such as app.example.com or www.example.com), Render requires a CNAME record:

• Type: CNAME
• Host/Name: app (or whatever subdomain you're configuring)
• Value/Target: Your Render service URL, e.g. your-service.onrender.com

For a root domain (apex domain, e.g. example.com), you cannot use a CNAME record per the DNS specification. Use Render's A records instead:

• Type: A
• Host/Name: @ or leave blank (represents the root domain)
• Value: 216.24.57.1

Some registrars support ALIAS or ANAME records at the apex — if yours does, you can point the root domain to your-service.onrender.com directly, which gives you automatic failover when Render updates its IP addresses.

Configuring DNS for Render Static Sites

Static sites on Render use the same DNS configuration as web services. Add a CNAME for subdomains pointing to your static site URL (your-site.onrender.com), or use the A record approach for the root domain. Render handles HTTPS automatically for static sites as well as web services — no additional DNS records for SSL are needed.

DNS for Render PostgreSQL and Private Services

Render's managed PostgreSQL databases use internal hostnames within Render's network and do not require external DNS records. If you expose a service to the public internet and want a custom domain, apply the standard CNAME or A record setup described above. Internal Render services that communicate service-to-service use Render's internal DNS automatically and are not accessible from the public internet regardless of DNS configuration.

SSL Certificates on Render

Render automatically provisions Let's Encrypt SSL certificates for custom domains. After you add a domain in the dashboard and configure the DNS records correctly, Render performs a DNS check and issues the certificate. This typically takes 5-30 minutes after DNS propagates. If the certificate is not issued after an hour, use the DNS propagation checker to verify your CNAME or A record is resolving globally. Render also supports wildcard certificates for domains where you host multiple subdomains — contact Render support for wildcard configuration.

Troubleshooting Render Custom Domain Issues

• Domain shows "Verifying" in Render dashboard: Render hasn't yet confirmed your DNS records point to its infrastructure. Wait for DNS propagation (check progress with the propagation checker) then click "Verify" again in the dashboard.
• Root domain not loading: Make sure you've configured an A record for @ (root), not just a CNAME for www. Check both records are active using the DNS lookup tool.
• Redirect loops: Render handles redirects between www and the root domain. Do not configure redirects independently at your registrar — let Render manage canonical URL routing after both DNS records point to Render.
• Service spun down (free tier): Render's free tier spins down inactive services after 15 minutes. This is not a DNS issue — the domain resolves correctly, but the first request after inactivity triggers a cold start. Upgrade to a paid plan for always-on availability.

For related DNS troubleshooting, see the DNS not propagating fix guide and the subdomain not working guide. Compare Render's DNS setup with Netlify DNS and Vercel DNS if you are evaluating platforms. Check DNS records across 50+ global servers using the propagation checker to confirm Render's records are live worldwide.