Step 1: Create your CNAME record
Create a CNAME record pointing your custom domain to exactly
cfdxy.heartbeat.chat.
Below is a list of popular hosting platforms and links that will show you how to create a CNAME record. If your platform isn't listed below, we recommend searching its help articles using the keyword "CNAME."
Cloudflare (Ensure that "Proxy" is disabled)
Godaddy (Ensure the 'host' field only contains your subdomain name and not the entire url)
Step 2: Confirm your CNAME Record
After creating your CNAME record, look up your CNAME record here:
If youâre able to confirm your CNAME record, you can move on to the next step. A successful CNAME record will result in a page that looks like this:
If your CNAME record has not been created successfully, you will see a page that looks like this:
If you canât confirm that your CNAME record exists, we suggest contacting your hosting platform to troubleshoot further.
Step 3: Confirm your new domain
Access your Heartbeat admin dashboard by clicking on the profile picture located at the bottom left corner of the sidebar.
Under the Customization tab, locate and click on Custom Domain.
Fill out the Custom Domain section & save your changes.
Troubleshooting
DNS Propagation Delays
Issue: When you point your custom domain to Heartbeat's servers, DNS changes might take some time to propagate. This means that even after setting it up correctly, you might not see the domain working immediately.
Resolution: DNS changes can take a few minutes to 48 hours to propagate fully. You can check DNS propagation using tools like
dnschecker.org.
Incorrect DNS Records
Issue: Often, custom domains don't work because the DNS records (A, CNAME, etc.) have not been configured properly or are pointing to the wrong addresses.
Resolution:
For custom domains, you must ensure that the A record points to the IP address provided by Heartbeat or a CNAME pointing to their hosted domain.
Double-check your DNS configuration in your domain registrar's dashboard.
If Heartbeat provides specific instructions on what DNS records to set, follow them exactly (e.g., A record, CNAME record).
Multiple CNAME or A Records Conflicts
Issue: Multiple CNAME or A records associated with the same domain can cause conflicts. This often happens when other services (e.g., email providers, and platforms) are also using subdomains or the root domain.
Resolution:
Ensure that your custom domain or subdomain has only one A or CNAME record pointing to Heartbeatâs servers.
If youâre using a subdomain, ensure that only the subdomainâs DNS record is updated and doesnât interfere with other services on the root domain.
Cache and Browser Issues
Issue: After DNS propagation and SSL certificate setup, sometimes browsers cache the old configuration, leading to the site still appearing down or not resolving correctly.
Resolution:
Clear your browserâs cache or try accessing the site from an incognito/private browser window.
You can also try loading the site from a different network or device to see if the cache is the issue.
Frequently Asked Questions:
How long does it take for DNS changes to propagate?
How long does it take for DNS changes to propagate?
DNS changes can take anywhere from immediately to a few minutes to propagate globally.
What should I do if my custom domain is not working?
What should I do if my custom domain is not working?
Double-check your DNS records for accuracy.
Ensure there are no typos in the domain names or IP addresses.
Verify that your DNS changes have fully propagated.
Contact Heartbeat.chat support for assistance if problems persist.
What happens if I change my domain registrar or DNS provider?
What happens if I change my domain registrar or DNS provider?
You will need to reconfigure your DNS records with the new provider to ensure your custom domain continues to point correctly to Heartbeat.chat.
Can I revert back to the default Heartbeat.chat domain?
Can I revert back to the default Heartbeat.chat domain?
Yes, you can always revert to the default Heartbeat.chat domain by removing or deactivating your custom domain settings in the Heartbeat.chat admin dashboard.