Free CNAME Record Lookup & Generator
Check if a CNAME record is configured for any domain, or get step-by-step instructions for adding one with your DNS provider.
- 1Log in to your Cloudflare dashboard
- 2Select the domain you want to configure
- 3Go to the DNS tab
- 4Click "Add record"
- 5Select "CNAME" as the type
- 6Enter the subdomain in the Name field (e.g., app)
- 7Enter the target in the Target field
- 8Set Proxy status to "DNS only" (grey cloud) for custom domain setups
- 9Click Save
Understanding CNAME Records
A CNAME (Canonical Name) record is a type of DNS record that maps an alias domain name to a canonical (true) domain name. When a DNS resolver encounters a CNAME record, it replaces the alias with the canonical name and continues the lookup process.
CNAME Records for Custom Domain Setups
CNAME records are the backbone of custom domain setups in SaaS platforms. When your users want to use their own domain (like app.theircompany.com) to access your platform, they add a CNAME record pointing their domain to your infrastructure (like custom.yourplatform.com).
The challenge for SaaS platforms is guiding users through this process, verifying the records are set up correctly, and handling edge cases like Cloudflare proxying, conflicting A records, and propagation delays. SaaSKevin provides an embeddable widget with guided setup and re-verification to handle this workflow reliably. You can use our DNS lookup tool to verify all record types for a domain.
Common CNAME Setup Issues
Cloudflare proxy mode: If your users use Cloudflare, the orange cloud (proxy) mode can interfere with custom domain verification. Users should set their CNAME to “DNS only” (grey cloud) during setup.
Root domain CNAMEs: Standard DNS doesn't support CNAME records on root domains. Users need to use a subdomain or leverage ALIAS/ANAME records if their DNS provider supports them.
Frequently Asked Questions
- What is a CNAME record?
- A CNAME (Canonical Name) record maps one domain name to another. For example, you can point app.yourdomain.com to your-app.provider.com. The CNAME acts as an alias, directing traffic from your domain to the target domain.
- How do I set up a CNAME for a custom domain?
- Log into your DNS provider (Cloudflare, Route 53, Google Cloud DNS, GoDaddy, Namecheap, and others), add a new CNAME record with your subdomain as the host and the target domain as the value. This tool provides step-by-step instructions for major DNS providers.
- Can I use a CNAME on a root domain?
- The DNS specification doesn't allow CNAME records on root domains (like example.com without a subdomain) because it conflicts with other records. Some DNS providers offer workarounds like ALIAS or ANAME records that provide similar functionality at the root.
- How long does CNAME propagation take?
- CNAME changes typically propagate within a few minutes to a few hours, but can take up to 48 hours in some cases. The propagation time depends on the TTL (Time To Live) set on the record and DNS caching across the internet.
- What is the difference between CNAME and A record?
- An A record maps a domain directly to an IP address, while a CNAME maps a domain to another domain name. CNAMEs are more flexible for custom domain setups because if the target server's IP changes, you don't need to update the CNAME record.
Need setup examples for real SaaS products? Browse our industry guides and explore all free domain tools.