How to Configure DNS Records for Render Web Services

Configuring render web services custom domain dns settings properly ensures your web applications load quickly, securely, and without SSL certificate errors. When you deploy an app to Render, it is assigned a default subdomain ending in onrender.com, but pointing your own custom domain requires mapping specific Apex or Subdomain DNS records at your domain registrar. Whether you are migrating an existing production app or launching a new project on example.com, following the correct DNS validation and routing steps is critical for zero downtime.

To verify your records and troubleshoot propagation issues instantly, you can use the DNS Lookup tool to check global name server responses and ensure your apex or subdomain points correctly to Render's infrastructure.

Understanding Render DNS Requirements

Render handles custom domains by requiring specific DNS records depending on whether you are configuring an apex domain (root domain) or a subdomain (like www or app). Unlike traditional hosts that rely solely on static IP addresses, modern cloud platforms often use dynamic routing layers that require CNAME flattening or specific IP targets.

Apex Domains vs. Subdomains

An apex domain (such as example.com) cannot natively have a CNAME record attached to it due to core DNS specifications (RFC 1033). To point an apex domain to Render, you must use A records mapped to Render's load balancer IP addresses. For subdomains (such as www.example.com or api.example.com), Render provides a target domain ending in onrender.com which you map using a standard CName record.

Required Record Types

• A Record: Maps your apex domain (example.com) directly to Render's IPv4 address.
• CNAME Record: Maps a subdomain (www.example.com) to your assigned Render service target.
• TXT Record: Used by Render to verify domain ownership before issuing Let's Encrypt SSL certificates.

Step-by-Step DNS Configuration Guide

Follow these sequential steps to map your custom domain to your Render web service. Note that provider-specific dashboard layouts vary, but the underlying DNS record types and values remain identical.

Step 1: Add the Domain in the Render Dashboard

1. Log into your Render Dashboard and select your web service.
2. Navigate to the Settings tab and scroll down to the Custom Domains section.
3. Click Add Custom Domain and enter your fully qualified domain name (e.g., www.example.com or example.com).
4. Render will generate the specific DNS records you need to create, along with a validation TXT record if required.

Step 2: Access Your DNS Provider

Log into the registrar or DNS hosting provider where your domain is registered (such as Cloudflare, Route 53, GoDaddy, or Namecheap). Navigate to the DNS management, DNS zone editor, or advanced DNS settings page. Note: Menu names and sidebar paths differ slightly depending on your provider, but you are looking for the table where DNS records are added and edited.

Step 3: Create the Ownership Validation TXT Record

Render requires ownership verification for security. Create a new TXT record using the details provided in your Render dashboard:

• Type: TXT
• Name / Host: _render-verify (or the specific string provided by Render)
• Value: A long alphanumeric verification string (e.g., render-verification-code=19202abc)
• TTL: Automatic or 300 seconds

Step 4: Configure Your Domain Records

Depending on whether you are using an apex domain or a subdomain, add one of the following record configurations.

Configuring a Subdomain (e.g., www.example.com)

Create a CNAME record pointing your subdomain to your Render application service URL:

• Type: CNAME
• Name / Host: www
• Value: your-service-name.onrender.com
• TTL: Auto

Configuring an Apex Domain (e.g., example.com)

Create A records pointing to Render's load balancer IP addresses. (Always consult your active Render dashboard for the exact current IPs, but standard Render routing uses addresses similar to 216.244.64.1 or equivalent cloud load balancer IPs).

• Type: A
• Name / Host: @ (or leave blank depending on your registrar)
• Value: 192.0.2.1 (Replace with Render's current provided IP)
• TTL: Auto

Command-Line Verification and Testing

Once your DNS records are saved, verify that they have propagated correctly using command-line utilities.

Checking DNS with dig

Run the dig command in your terminal to inspect the CNAME or A records for your domain:

dig CNAME www.example.com +short

Expected output:

your-service-name.onrender.com.

For apex domains, check the A record:

dig A example.com +short

Expected output:

192.0.2.1

Verifying SSL and HTTPS with curl

After DNS propagation completes (which can take anywhere from a few minutes to a few hours), test the HTTPS response using curl:

curl -Iv https://www.example.com

Sample successful output showing valid TLS handshake and Render headers:

* Connected to www.example.com (192.0.2.1) port 443 (#0)
* SSL certificate verify ok.
< HTTP/2 200 
< server: Render

DNS Configuration Comparison

Domain Type	Record Type	Host / Name	Target / Value	Purpose
Subdomain	CNAME	www	app.onrender.com	Routes web traffic to Render
Apex Domain	A	@	192.0.2.1	Points root domain to Render IP
Validation	TXT	_render-verify	render-verification-code=...	Proves domain ownership

Common Mistakes and How to Fix Them

• Conflicting CNAME and Apex Records: Creating a CNAME record on an apex domain (example.com) violates DNS standards and will break email or web traffic. Always use A records for the root domain.
• Missing SSL Provisioning: Render automatically provisions free Let's Encrypt certificates, but this fails if the ownership TXT record is incorrect or if DNS has not fully propagated.
• Proxy Orange-Clouding (Cloudflare): If you route your Render traffic through Cloudflare, ensure your SSL/TLS encryption mode is set to Full or Full (Strict) to avoid endless redirect loops.

Quick DNS Setup Checklist

• Added the custom domain inside the Render dashboard settings.
• Created the ownership verification TXT record.
• Added the correct CNAME record for subdomains or A records for apex domains.
• Verified record propagation using dig or an online DNS lookup utility.
• Confirmed successful HTTPS loading and valid SSL certificate generation.