Blog Domain Configurations

Before configuration

See your account settings for custom domain availability for your podcast. For a custom subdomain, create a CNAME record with your DNS provider. Use your podcast's Podigee address as the target, for example my-podcast.podigee.io. Replace my-podcast with your podcast's subdomain. If the custom domain option is missing from your account, contact support.

For a published podcast, blog and feed URLs can become different. Record the existing URLs first. Make a plan for redirects from the old feed URLs. After configuration, make sure that the blog, feed, audio and embedded players work. Keep old URLs and redirects until their continued use is clear.

Domain field format

Enter only the hostname, for example example.com or podcast.example.com. Do not include http://, https:// or a path such as /podcast.

A saved hostname is not a completed DNS or HTTPS configuration. After configuration, open the new URL with https:// in your browser. Make sure that it works without a certificate warning. If an error occurs, give support the domain and the exact error message.

Domain types

There are two possible domain configurations available to your podcast, including:

  1. A subdomain like www.example.com or podcast.example.com
  2. A root domain like example.com

To add them, you need to follow a simple two-step process:

  1. Tell Podigee which domain you would like to use.
  2. Configure your domain's DNS to point to Podigee.

Find specific instructions for each domain configuration below.

DNS example only: The names and targets below are examples. Do not copy example.podigee.io as the target for your podcast. Use your podcast's actual Podigee subdomain instead, for example my-podcast.podigee.io. Not all DNS providers support ALIAS or ANAME records.

Adding a subdomain of your domain

If you entered a subdomain (like www.example.com) you need to go to the provider where you registered your domain (or your DNS provider) and create a CNAME record for that domain pointing to your subdomain.

For example, if your domain name is www.example.com and your Podigee subdomain is example.podigee.io this is how the record should look:

  • Record type: CNAME
  • Entry: www
  • Target: example.podigee.io

Once you have done this, you can move on to the section labeled Configure the domain in Podigee below ⬇️

Adding a root domain

Adding a root domain like example.com is unfortunately not possible with every Domain/DNS provider. Here are two providers that support it:

According to the example above, you would have to make the following settings in order to use the root domain:

  • Record type: ALIAS or ANAME
  • Entry: <empty> or @
  • Target: example.podigee.io

If your provider does not support this, you need to use a subdomain instead, e.g.  www.example.com. Our recommendation in that case would be to redirect your root domain to the subdomain you decide to use, like example.com → www.example.com.

Once you have done this, move to the section labeled " Configure the domain in Podigee" below.

🛠️ Configure the domain in Podigee

DNS updates take different amounts of time with different providers and caches. A DNS result does not show that HTTPS is ready. Examine DNS and HTTPS separately. There is no fixed one-hour completion time.

To add the domain to your podcast, go to podcast overview page and click on the name of the podcast you want to use the domain with.

Then go to the tab " Blog" and enter your domain name into the "Domain" field. 

Domain field in the blog settings; the view can be different in your account

Then open the new blog URL with HTTPS. If a certificate warning appears, contact support before you give the URL to listeners or platforms.

An automatic blog redirect does not show that feed redirects are correct. Examine the old feed URLs and their destinations separately. Contact support if a redirect goes to an incorrect destination.

Need help?

If you need any help setting up your domains, please email us the name of your domain provider, and we'll try to help you as soon as we can.


Use a subdomain of podigee.io

Published podcast: Before you replace the subdomain, make a plan for redirects from the old feed URLs and for the necessary adjustments to embedded players.

To get started quickly or if you don't want to register your domain name you can use a subdomain provided by us, which looks something like this:

https://my-podcast.podigee.io

The part between the protocol https:// and the domain podigee.io is the so-called subdomain. In the example from above the subdomain is my-podcast. This subdomain can be configured by you in the podcast settings.

To do this, go to the podcast overview page and click on the name of the podcast you want to edit. Choose the tab "General". After creating a new podcast, the name for the subdomain will be set to a randomized one (podcast5f5e12 like in the following image ). In order to change this name to a more suitable one, click in the area with the lock symbol and the text "Click to unlock" next to it.

Podigee subdomain name field in the general settings

The field with the grey background will be unlocked and rendered editable. Select the whole text in the field "Name (subdomain)" and enter your desired subdomain name. The preview below the input field will reflect the final web address for your podcast blog.

If the desired subdomain is already in use, you will see an error message. In this case, you have to think about a new desired subdomain that you'd like to use instead.

❗️ Your subdomain can be any combination of letters, numbers and dashes. Any other kind of special characters are NOT allowed. So my-great-podcast is fine, while my.great.podcast is not because it contains dots. Please also watch out to only enter the subdomain, you don't need to type in .podigee.io, because the system will automatically complete this.

HTTPS and certificates

Podigee provides the HTTPS certificate for your custom domain automatically. Save the hostname in Podigee and configure DNS to point the domain to Podigee. Then open the HTTPS address. The domain must be publicly reachable for certificate validation, and HTTP requests must also reach Podigee. You do not need to upload your own certificate.

DNS changes and certificate issuance can take time. Check that the address works without a certificate warning. If it does not, send support the hostname and error message. Do not use a fixed server IP as the DNS target.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.