Booking page custom domain: a step-by-step setup guide

A booking page custom domain puts your scheduling page on your own address, like book.yourfirm.com, instead of the vendor's. Setup usually takes one DNS record, a verification step and an HTTPS certificate. The hard part is doing it without breaking your website or email, so this guide covers safe setup, testing and rollback.

We use book.example.com as the example throughout. It's a placeholder, not a real Caletus address, and there are no sample DNS values here to copy into a live account.

Booking page custom domain, vendor link or embed?

Pointing a subdomain at your booking page is different from a redirect. A redirect sends visitors on to the vendor's address, so the browser bar changes. Decide which one you want: a short link people remember, or a booking page that stays on your address the whole way through. You'll test them differently.

What to prepare before you touch DNS

• Confirm your scheduler supports a custom domain on your plan, and get its current setup steps.
• Find out who manages DNS for your domain. That isn't always the company you bought the domain from.
• Pick an unused subdomain, like book or meet, and check that nothing else is running on it.
• Keep your current booking link working, save a copy of your DNS settings, and name someone who can approve or undo the change.

Two DNS record types come up most. A CNAME points one hostname at another, and a TXT record stores text, often for verification. Add only the record types and values your scheduler asks for.^[1]

Use a separate subdomain for booking instead of replacing your main website address. Ask whoever manages your domain to review the change. Leave mail records, nameservers and unrelated website records alone.

Custom domains in Caletus: what to have ready

Caletus supports custom domains as well as personalized caletus.com links for your Caletus booking pages. You add a CNAME record that points your subdomain to Caletus, and Caletus sets up HTTPS for you. The exact CNAME target appears in your Caletus domain settings, so copy it from there.^[2]

Your own domain comes with Caletus's Professional plan ($6 per user per month billed yearly) and with Enterprise. Free accounts use an caletus.com/yourname link. The white label branding page lists what else comes with it, like removing the Caletus badge.^[3]

If anything is unclear, ask support before you edit records. A useful message: "We'd like to use book.example.com for our booking page. Can you confirm it's on our plan, the exact records we need, whether a proxy is supported, how HTTPS is set up, and how to disconnect the domain safely?" Swap in your own subdomain.

How to connect your booking subdomain, step by step

1. 1Write down the subdomain and the booking page it should show. Check whether it maps to your whole account or to one meeting type.
2. 2Add the subdomain in your scheduler's domain settings, if that step comes before verification.
3. 3Open your active DNS zone and add only the record type, name and value you were given.
4. 4Save a note of the change. Run the verification step and read the status before you edit anything again.
5. 5Once verification and HTTPS are done, test a real booking before you change any links on your website.

DNS dashboards split each record into a name and a target (sometimes called content), and some also show proxy and TTL settings. Follow your DNS provider's format. Some want just "book" as the name, while others want the full book.example.com.^[4]

Never guess a CNAME target, such as the vendor's homepage address. A familiar address usually isn't the service endpoint. Verification values work the same way: a token copied from someone else's tutorial won't prove you control your subdomain.

DNS verification and HTTPS are two separate checks

DNS answers get cached for as long as their time to live (TTL) allows. So a changed record can show up at different times for different people. A short TTL doesn't promise that the whole setup, including the vendor's verification, will finish by a set time.^[5]

HTTPS uses TLS to protect the connection, and the certificate has to match the address the visitor opens. A DNS record pointing at the right service doesn't mean the certificate is ready yet.^[6]

Don't share the new address while it shows a certificate warning, a verification page or the wrong account. Keep using your current booking link. Also avoid changing settings again and again while verification runs, or you won't know which version you're testing.

Test a full booking before you switch links

Use a reserved test slot and made-up attendee details. Keep the test appointment long enough to check the confirmation and reschedule links, then delete it. A page that loads can still point to the wrong meeting type or send the wrong location.

Booking domain DNS problems and what to check first

When you contact support, send the subdomain, the error you saw, the time of the test and screenshots of the record and status with private details hidden. Never share registrar passwords, access tokens, full DNS exports or attendee details in public forums. Change only the record you're looking into.

Write a short handover note

Note the domain owner, DNS provider, booking page owner, approved subdomain and support contact. Store the setup steps with the change record, not in someone's private chat. Include the original booking link and your test results, so the next person can restore access without starting over.

Agree who checks the setup after a domain transfer, a scheduler switch or a billing change. Ask the vendor what happens if the feature gets turned off and who renews the certificate. Write down the real answers or mark them as open questions, and hold off on a wider rollout until the important ones are answered.

Keep a rollback plan ready

If something goes wrong, first point your website buttons and new emails back at the old booking link. Then undo only the records you changed, using your saved settings and the vendor's disconnect steps. Agree on the order with your DNS admin so the subdomain isn't left pointing at nothing.

Undoing DNS won't fix links already sent in confirmations, so check existing appointments separately. Tell affected clients which link to use, and keep notes on how the old and new addresses behave until the switch is complete.

A custom booking domain should be a small, careful change. Keep the working link live, use the exact records you're given, and launch only after a full test booking goes through. For the rest of the branding checklist, read our guide to white label appointment scheduling.

• custom booking domain
• booking subdomain setup
• booking domain DNS
• branded scheduling URL