When you connect a custom domain to Bouncy, you need to add DNS records at your domain registrar. This article explains what each record does and how to set them up correctly.
What is DNS?
DNS (Domain Name System) is the system that translates domain names (like yourbrand.com) into the IP addresses that computers use to communicate. When you add DNS records, you're telling the internet where to send traffic for your domain.
Records Required by Bouncy
Bouncy requires two DNS records for each custom domain:
A record or CNAME record — directs traffic to Bouncy's servers
TXT record — proves you own the domain
Root Domains vs Subdomains
The type of pointing record you need depends on whether you're connecting a root domain or a subdomain.
Root Domain Setup (e.g., yourbrand.com)
Root domains (also called apex domains or naked domains) use an A record because the DNS standard doesn't allow CNAME records at the root level.
Record Type | Host/Name | Value | TTL |
A |
| The IP shown on your Custom Domains page | Auto or 3600 |
The
@symbol represents the root of your domainThe A record points your domain to Bouncy's IP address
Subdomain Setup (e.g., links.yourbrand.com)
Subdomains use a CNAME record, which aliases your subdomain to Bouncy's DNS.
Record Type | Host/Name | Value | TTL |
CNAME |
| The CNAME target shown on your Custom Domains page | Auto or 3600 |
The CNAME host is just the subdomain part (e.g.,
links), not the full domainSome registrars require the full hostname (e.g.,
links.yourbrand.com) — check your registrar's documentation
Understanding Each Record Type
A Record
An A record maps a domain name directly to an IPv4 address. When you add the A record shown on your Custom Domains page, you're telling DNS to send all traffic for your domain to Bouncy's servers. The IP can differ per domain, so always copy the value from your dashboard.
CNAME Record
A CNAME (Canonical Name) record creates an alias from your subdomain to another domain. By pointing to the CNAME target shown for your domain, your subdomain inherits the IP configuration managed by Bouncy's infrastructure. Each domain gets its own target, so copy it from your dashboard.
TXT Record
A TXT record stores text data in DNS. You only need one if your domain was previously connected to another platform: in that case an extra ownership TXT record appears on your Custom Domains page. Add it exactly as displayed.
How to Add DNS Records (By Registrar)
The exact steps vary by registrar, but the general process is:
Log in to your domain registrar's control panel
Find the DNS Management or DNS Settings section
Click Add Record or Create Record
Select the record type (A, CNAME, or TXT)
Enter the host/name and value as shown above
Save the record
Common Registrar Guides
GoDaddy: Domains > DNS Management > Add Record
Namecheap: Domain List > Manage > Advanced DNS > Add New Record
Cloudflare: DNS > Records > Add Record (disable the proxy/orange cloud for the record)
Google Domains: DNS > Custom Records > Manage > Create New Record
Squarespace Domains: Settings > Domains > DNS Settings > Add Record
Cloudflare users: Make sure the proxy (orange cloud icon) is turned off for your A or CNAME record. The record should show a grey cloud (DNS only). Proxying traffic through Cloudflare will interfere with Bouncy's domain verification and SSL provisioning.
TTL (Time To Live)
TTL controls how long DNS resolvers cache your record. For initial setup, a lower TTL (e.g., 300 seconds / 5 minutes) means changes propagate faster. After verification, you can increase it to 3600 (1 hour) or leave it on Auto.
Verifying Your Records
After adding DNS records, wait for propagation (typically 15-30 minutes, up to 48 hours) and then use Bouncy's Verify button or the built-in DNS Propagation Checker to confirm your records are live.
Common Mistakes
Adding a CNAME at the root — most DNS providers don't support this; use an A record instead
Including the full domain in the host field — some registrars auto-append the domain, so entering
links.yourbrand.commay createlinks.yourbrand.com.yourbrand.comLeaving Cloudflare proxy enabled — this intercepts traffic and prevents Bouncy from issuing SSL certificates
Existing conflicting records — remove any existing A or CNAME records for the same host before adding the Bouncy ones
What's Next?