Skip to main content

Set up a custom domain

Use an address such as sermons.example.church for your public sermon site, feed, and links.

A custom domain is optional. Your standard yetanothersermon.host/_/your-church/ address continues to work without one.

Only an Admin can change the custom domain. You also need access to the DNS records for the church's domain, so if someone else looks after your website or email, ask them to make the DNS change.

1. Choose the hostname​

Use a subdomain dedicated to the sermon library, such as:

  • sermons.example.church
  • media.example.org
  • listen.example.com

Leave out https://, any path, and any trailing slash when you enter the hostname.

2. Add the DNS record​

At the provider that manages the domain's DNS, create this record:

SettingValue for sermons.example.church
TypeCNAME
Name or Hostsermons
Target, Value, or Points tocname.yetanothersermon.host
TTLAutomatic or the provider default

The Name is the part before the church's domain, so for listen.example.com you enter listen. Some providers want the complete hostname instead, in which case enter listen.example.com.

Do not point the record to yetanothersermon.host or to your church's standard public URL. The CNAME target must be exactly:

cname.yetanothersermon.host

Remove any existing A, AAAA, or CNAME record with the same name first. Two records for one name will conflict.

Cloudflare​

In Cloudflare:

  1. Select the domain, then go to DNS > Records.
  2. Select Add record.
  3. Choose CNAME and enter the name and target above.
  4. Set Proxy status to DNS only, shown as a grey cloud.
  5. Select Save.

Use DNS-only mode, because we validate the hostname and manage HTTPS for it ourselves. Cloudflare explains the difference in its proxy status documentation.

3. Save the domain in Yet Another Sermon Host​

  1. Go to Settings > General, or open general settings directly.
  2. Enter the complete hostname, such as sermons.example.church, in Custom domain.
  3. Select Save Settings.
General settings with sermons.example.church entered in the Custom domain field

Saving the domain starts a check over HTTPS to confirm that the hostname reaches your church's site. If it is not ready yet, we keep trying, so you do not need to save it again.

4. Allow DNS to propagate​

DNS changes are not visible everywhere straight away. Give the CNAME time to propagate, especially if you replaced an existing record.

You can check from a terminal with:

dig CNAME sermons.example.church

The result should end up pointing at cname.yetanothersermon.host. An online DNS lookup tool will show whether different parts of the world can see the new record yet.

5. Test the public site and HTTPS​

  1. In Yet Another Sermon Host, select Public View.
  2. Confirm that the browser opens https:// followed by the custom hostname.
  3. Open a sermon and play its audio.
  4. Open Subscribe and test the RSS feed.
  5. Test again in a private browser window so an existing login or cache does not hide a problem.

We issue and renew the HTTPS certificate automatically, so there is nothing to buy or upload. Once everything is working, your public links and feeds use the custom hostname.

Change or remove the domain​

To change it, update the DNS record first, then save the new hostname under Settings > General and repeat the tests.

To remove it, clear Custom domain and select Save Settings. Delete the old DNS record once your standard public address works again.

If this did not work​

  • The Custom domain value is rejected: Enter a plain hostname, with no https://, spaces, port, or path.
  • The browser says the domain cannot be found: Check the CNAME name and target, remove any conflicting records, and give DNS more time to propagate.
  • Cloudflare shows an error or the site reaches the wrong server: Set Proxy status to DNS only and confirm the target is cname.yetanothersermon.host.
  • The site loads but validation keeps failing: Test the public site over HTTPS in a private window, then email us at admin@yetanothersermon.host with the custom hostname.
  • HTTPS shows a certificate warning: Do not click past the warning. Recheck DNS, give the certificate time to be issued, then email us at admin@yetanothersermon.host if it continues.