How to add a Custom Domain
To connect your own custom domain, a simple configuration is necessary both on your domain registrar and via the Podcastpage dashboard. (if you don't have a domain name, you'll have to purchase one through one of the popular registrars like Namecheap, Google Domains, etc.)
Once you're ready to connect your domain, please follow the steps below -
5 Steps to connect your domain to Podcastpage
- Go to your domain registrar's control panel (where you bought the domain) and find the DNS settings.
- Remove or delete any existing "A", "CNAME", or "AAAA" records that have "@" (or a blank host value) as the host name.
- Add a new "A Record" and point it to our server's IP address - (under the "Value" field)
4. Once you update the domain DNS settings, add that custom domain in your Podcastpage dashboard ( without http/https or www), and hit the save button. If you've configured everything properly, this might take about a minute to fully work. In case something is not working, you can check your actual domain DNS and see if the "A Record" points to another address - https://dnschecker.org/ - or contact us directly.
Note - Usually this process takes less than a few minutes. In rare cases, it can take up to 48 hours for your DNS to fully propagate. If you're having any issues, go back over the previous steps and check that you have configured everything properly. You can also reach out to us directly for support.
Domains & DNS - More info from your registrar's docs
For more details and examples regarding DNS setup, please refer to the examples below in popular domain registrars: ( if your registrar isn't listed here, don't worry, any registrar will work, just find their docs and configure everything as mentioned above)
- Google Domains
- Network Solutions
- Rackspace Cloud DNS
We typically recommend that you use the " Naked Domain" as your default custom domain. This means you use the actual domain name, (like domain-name.com) and not a www version of it (like www.domain-name.com).
With that said, it's fully possible to use the www version instead, or obviously use both options.
Using a WWW Domain
To use www for your custom domain, simply remove all other existing records with "www" as the Host, and add a new one pointing to your Podcastpage.io subdomain. See the example below -
Important - replace the " my-subdomain" value seen below with your actual Podcastpage subdomain.
Using both WWW and non-WWW domains
If you're using a custom domain, you may want to redirect your domain from the non-www version to the www version (or the other way around, it's up to you to decide) to ensure your visitors are always reaching your site, regardless of if they're using the www subdomain or not.
This is often called a " Domain Redirect" or "Domain Forward". The vast majority of the domain registrars support this method. Here are a few more resources regarding domain redirects/forwards from popular registrars -
Note - If your domain registrar doesn't seem to support forwards or redirects, contact us and we'd be happy to help find a solution.
Custom Sub Domains
Some companies or website owners choose to create their podcast site alongside their main website (for example: https://podcast.yourdomain.com).
To set this up, you'll have to add a subdomain (like "podcast", "pod", or any other subdomain of your choice) and point it to your Podcastpage subdomain.
This can also be used as a sub-page of your existing site, and you can work to match the layout with the existing style you have on the original site.
Important - replace the "my-subdomain" value seen below with your actual Podcastpage subdomain.
Other DNS and Domain options
If you are using CloudFlare, CloudFront, or other cloud DNS/CDN management services, please make sure to use their "DNS-Only" option.
Podcastpage automatically creates SSL certificates for your custom domains, along with CDN & caching, so you don't have to worry about those through external platforms.
It's also possible to use CloudFlare's SSL certificates instead of the certificates we provide. If that's what you're after, follow these steps -
- Stop Cloudflare on your domain.
- Set up your DNS as described above (without CloudFlare) and wait until you receive our SSL certificate.
- Go back and re-activate CloudFlare with the Full SSL mode.