Setting up a Custom Root Domain
Step 1: Add your A record
Access the DNS settings where your domain is managed. The A record (Address Record) maps a domain name to its corresponding IP address, allowing users to connect to the server hosting the website. Hereâs how you can view the A record:
Your hosting provider should have documentation telling you how to do this.
Create an A record pointing from your domain to 188.93.147.211.
You need to make sure that there are no conflicting records set for the same host and remove them if there are any. The records you need to check may be of Unmasked/Masked/Permanent Redirect, A, or CNAME record types.
You can Google â<your hosting provider> add A recordâ to try finding this documentation.
Step 2: Confirm your A record
After setting up your A Record, confirm that it exists here: https://www.nslookup.io/
If no records are found and you are unable to confirm that your A record exists, we suggest contacting your hosting platform to troubleshoot further.
If you have multiple IPs associated with the A record, then youâll need to delete the non-Heartbeat one before moving forward.
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 with your root domain & 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.
Some DNS systems, such as Namecheap's, automatically append the domain name to the values entered during record creation. Ensure that you do not include the domain name twice in your entries.
For instance, if you need to create subdomain.domain.tld, simply enter 'subdomain' as the value, not the full 'subdomain.domain.tld'.
If you use Namecheap Basic nameservers or PremiumDNS, remove the "domain.tld" portion from the Host value before adding it to the validation record. Copy the Host and Target values and paste them into the corresponding fields in your DNS provider account. Also, set the TTL value to the minimum allowed.