Use your own domain

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.

See Blog domain configuration for the full procedure.

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.