Setting Up Your Custom Domain

Updated 1 week ago by Eric Lutz

Please note: This is an advanced feature, and requires that you are comfortable with making changes to your domain's DNS records. The Church Online Platform will generate a TLS certificate for your domain at no cost.

1. Set up your DNS

  1. Create a CNAME for your Custom Domain that points to ingress.online.church.

Example:

  • Host: Custom domain (e.g.: live.example.church)
  • Points to: ingress.online.church
  • TTL (Time to Live): 1 hour is a good default

For more detailed instructions, check with your specific DNS provider.

2. Add your Custom Domain to the Platform

  1. From the Admin, go to Setup > Domain.
  2. Enter the Custom Domain you want to use for the Church Online Platform and save your changes, for example “live.example.church”.

Once you've added a Custom Domain you will be able to check the status. Please note: it can take up to 10 minutes for your DNS changes to take effect, though our system will know about the new settings immediately.

FAQs

My Custom Domain is set up correctly but is still directing to it's previous target.

- DNS settings define the IP address to which a domain name (e.g. live.example.church) points. Those settings have an attribute called TTL which stands for “Time To Live”; that might be set to 1 hour meaning that a user’s ISP might remember the DNS setting for an hour, instead of checking every time to see if the value has changed. That all means that DNS settings can take a variable amount of time to take effect - that’s a good thing in terms of performance for the user, but a constraint in terms of how quickly a change takes effect.

- If you are using Cloudflare as your DNS host, please make sure that you setup your domain has “DNS only” and not proxied.

Can I use a root domain, such as examplechurch.com or example.church?

No, we are only able to support a subdomain such as live.examplechurch.com or live.example.church. However, you can use your DNS provider to point that domain to your instance of the Platform.


How did we do?


Powered by HelpDocs (opens in a new tab)