Custom Domain

Serve your booking site from your own hostname — adding the domain, the DNS records the PMS gives you, verification, HTTPS and each status.

Every property gets your-slug.book.innvera.io the moment the engine is turned on, and it keeps working forever. Adding your own hostname — book.yourhotel.com, say — gives guests an address that matches your website and keeps them inside your brand from link to confirmation.

Open Settings → Booking Engine and choose Domains in the setup rail. You need write access to the booking engine permission to add or remove one.

Where it lives

The panel has two parts:

Your domains — "Default subdomain is issued when you turn the engine on." One row per hostname, with its status badge, the DNS records to set, and a delete button on everything except the default.
Add a custom domain — a Hostname field and an Add domain button.

Your default subdomain carries a Default badge and has no delete button: it is the address Innvera falls back to, and the one used in confirmation emails when nothing else is live.

Add your domain

Decide on the hostname

A subdomain such as book.yourhotel.com or reservations.yourhotel.com is the usual choice, and the easiest to point at us. An apex domain (yourhotel.com with nothing in front) works too, but it takes an A record and you will be moving your main website's DNS — do that only if the booking site is your website.

Add it in the PMS

Type the hostname into Hostname — no https://, no trailing slash — and click Add domain. Case does not matter; it is lower-cased for you.

Innvera registers the hostname with the storefront's hosting platform first and only then saves the row, so a failure leaves nothing half-created for you to clean up. You may see:

Message	What it means
`This hostname is already in use`	Another property — or an earlier attempt of yours — already claims it. Remove it there first.
`Vercel is not configured in this environment…`	Hosting credentials are missing on this deployment. Nothing you can fix from the PMS; tell your administrator.
A gateway error naming the hosting provider	The provider rejected the hostname or was unreachable. The wording is passed through verbatim; read it, fix the cause, and add the domain again.

A toast confirms Domain added and the row appears with its status and DNS records.

Copy the DNS records

Each record is shown as TYPE NAME → VALUE with a copy button. Take them to wherever your domain's DNS is managed — your registrar, Cloudflare, Route 53 — and create them exactly as given. See the next section for what to expect.

Wait, then confirm

DNS changes take anywhere from a few minutes to a few hours to spread. Once they have, the row's status moves to LIVE and the hostname serves your published site over HTTPS.

The DNS records

The records in the panel are built for your specific hostname, so copy them rather than reusing an example.

For a subdomain (anything with a label in front of your domain) you get one CNAME:

CNAME   book   →   bb6a7c8019590084.vercel-dns-016.com

The NAME is the part in front of your domain — book for book.yourhotel.com. The VALUE is the target our hosting project is assigned; newer projects get their own target rather than a generic one, which is exactly why you should copy the value the panel shows instead of one you have seen elsewhere.

For an apex domain you get an A record instead:

A   @   →   76.76.21.21

@ means the domain itself. Some DNS providers write this as a blank name or as the full domain — follow their convention.

Verification records. If the hostname has been claimed on the hosting platform before, one or more TXT records appear above the routing record. Set those first: nothing else takes effect until ownership is proven.

Do not proxy the record

If your DNS is on Cloudflare, the record must be DNS only — the grey cloud, not the orange one. With proxying on, Cloudflare terminates TLS itself and the certificate for your booking site can never be issued, which shows up as certificate warnings or redirect loops for guests.

Leave your website's own records alone

Adding a CNAME for book does not touch www or your apex. Your existing website carries on exactly as before.

Statuses

Badge	Meaning	What to do
`PENDING`	The hostname is recorded but not yet registered with the hosting platform.	Press Publish site — publishing retries every pending or errored domain.
`VERIFYING`	Registered, waiting for the ownership challenge.	Set the `TXT` records shown on the row.
`VERIFIED`	Ownership is confirmed, but traffic is not routing to us yet.	Check the `CNAME` or `A` record, and that it is not proxied.
`LIVE`	Fully working. Guests can reach your site here.	Nothing.
`ERROR`	The last check against the hosting provider failed.	Read the error, fix the cause, then publish again to retry.

Certificates and HTTPS

There is nothing to buy, upload or renew. Once the domain verifies, a certificate is issued and renewed automatically, and the site is served over HTTPS. Until then guests reaching the hostname may see a certificate warning — which is the main reason not to advertise a new domain until its row says LIVE.

Propagation and re-checking

A row's status is recorded when the domain is added and re-checked when you publish. It does not poll on its own, so a domain that went live at your DNS provider twenty minutes ago may still read VERIFYING until something prompts a fresh check.

Re-check button — coming soon

A per-domain re-check action exists in the platform but is not yet wired into the Domains panel. For now, press Publish site after your DNS has propagated: publishing re-registers every pending or errored domain and refreshes what the panel shows. Reloading the page alone will not change a status.

A hostname that points at us but is not attached to any enabled property answers with a plain message — "This address isn't connected to a hotel yet." Seeing that means the DNS side is working and the PMS side is not, which is a much easier problem than the other way round.

Remove a domain

Click the bin icon on the row and confirm: "Remove this domain? Guests will no longer reach your booking site on this hostname." The hostname stops resolving to your property at once, so remove your own DNS record too if you are not reusing it.

The default subdomain cannot be removed. To take the whole site down, turn the engine off from the ⋯ menu instead — that stops every hostname, custom domains included, without deleting anything.

Common mistakes

Proxying the record. An orange cloud on Cloudflare blocks certificate issuance. DNS only, always.
Adding the domain before the DNS record exists. It is not an error — the row simply sits at VERIFYING — but it is easier to create the record first and add the hostname second.
Typing https://book.yourhotel.com. The field wants a hostname, not a URL.
Expecting the status to catch up by itself. Publish again after your DNS has propagated.
Advertising the domain before it is LIVE. Guests hit a certificate warning and do not come back.

On this page