How to add a Custom Domain
To connect your own custom domain, you'll need to make a few changes on both 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, GoDaddy, etc.)
If you're trying to connect a subdomain to an existing website/domain, skip to the "Custom Sub Domains" section below
How to connect your main domain to Podcastpage in 4 easy steps
- 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 "@", "WWW" or a blank host value as the host name. If your domain has forwards or redirects - remove those as well.
- Add two new "A Records" and point those to our server's IP address - (under the "Value" field)
| Type | Host / Name | Value / Data |
|---|---|---|
| A | @ | 37.16.0.118 |
| CNAME | WWW | domains.podcastpage.io |
(You can leave the TTL option with the default value, or use "Auto".)
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
- NameCheap
- GoDaddy
- IONOS
- Hover
- Network Solutions
- Rackspace Cloud DNS
- Squarespace
- Bluehost
Custom Sub Domains
Many companies or website owners decide to set up their podcast site alongside their main website (for example: podcast.yourdomain.com while the main website is separately managed on "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-podcast" value seen below with your actual Podcastpage subdomain.
If you prefer, you can add a CNAME record instead of the "A" record. In that case, you'll have to set the value to your site's subdomain on the Podcastpage.io domain.
| Type | Host / Name | Value / Data |
|---|---|---|
| CNAME | my-podcast | domains.podcastpage.io |
Other DNS and Domain options
If you are using CloudFlare,, or other cloud DNS/CDN management services, please make sure to use their "DNS-Only" option and avoid using proxy servers or custom SSL certificates.
Podcastpage automatically creates SSL certificates for your custom domains, along with CDN & caching, so you don't have to worry about getting 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.
Migrating from older configurations
If you're using the old IP values in your DNS "A" records (151.139.128.10), you'll need to update your records with the new IP address mentioned above. The correct IP is 37.16.0.118
Please do so at your earliest convenience, as keeping the old IP can eventually lead to downtime.
If your domain was only connected via WWW - you're now advised to connect both the root domain (non-WWW) and the WWW domain as described on this page.
(also, remember remove the WWW from the custom domain field in your Podcastpage dashboard)