How to Setup Your DNS for VibeSites
This article covers how to add CNAME records for your DNS in order to launch VibeSites in MultiHub
Overview
Every VibeSites property or landing page hosted through MultiHub needs one CNAME record in your DNS provider so your custom domain points to the Cloudflare Pages site that serves your VibeSite.
This guide walks you through it end to end: creating custom domains in MultiHub, adding the CNAME in your DNS provider, and verifying propagation.
What You'll Need
- Access to your DNS provider account (where the property domain is registered)
- Access to MultiHub, or an exported CNAME records spreadsheet from your Repli team
Step 1 - Create Custom Domains in MultiHub
If you already have a CNAME records list or your domains are already set up in MultiHub, skip to Step 2.
Option A - Manage domains at the company level (recommended for bulk setup)
- In MultiHub, open the Vibesites workspace and navigate to the Domains tab (Company Vibesite Domains page).
- In the Domains column for any property, click Add Domain.

Option B - Manage domains one property at a time
- Open the property in MultiHub and navigate to Vibesites, then Domains (Property Vibesite Domains page).
- Click + Add Domain in the Custom Domains section.

When the Add Custom Domain dialog opens
- MultiHub auto-suggests a www. prefix for property websites or rentnow. for landing pages, based on the site type.
- The suggested domain uses the property website already on file in MultiHub. If it's wrong, type the correct hostname in the input, or click the pencil icon next to the property URL to update it in MultiHub.
- This domain will be set as the primary domain for the site (you can change this later).
- Click Add Domain.

Once added, MultiHub shows the domain with a confirmation status and the exact CNAME record you need to enter at your DNS provider.
Optional - Export the full CNAME list for your IT team
From the Company Vibesite Domains page, click the Actions dropdown, then Export CNAME Records. This gives you a spreadsheet you can hand off to whoever manages DNS.
Step 2 - Add the CNAME Record at Your DNS Provider
Using either the exported spreadsheet or the values shown in MultiHub, add a CNAME record for each property domain.
Important: Make sure there is only one CNAME record for a given Name (rentnow or www) per domain. Duplicate records are the most common cause of misconfiguration.
Fill in the DNS record fields as follows:
| Field | What to Enter |
| Type | Select CNAME from the dropdown |
| Name | rentnow (landing page) or www (property website) |
| Value | Paste the value from MultiHub or the CSV (e.g. site-acacia-park-apts.pages.dev) |
| TTL | Leave as default (1 Hour) |
Click Save.

Step 3 - Verify at Your DNS Provider and Move to the Next Domain
- Confirm the new CNAME record appears in your DNS records list.
- Repeat Step 2 for each remaining property.
Example
For the domain acaciaparkapartmentselpaso.com, the CNAME record looks like:
| Type | Name | Value |
| CNAME | rentnow | site-acacia-park-apts.pages.dev |
This makes rentnow.acaciaparkapartmentselpaso.com resolve to the Cloudflare Pages site serving your VibeSite.
Step 4 - Verify in MultiHub
- Return to the Company or Property Vibesite Domains page in MultiHub.
- Click the Refresh button next to the domain to check propagation.
- When the domain status shows Active (green), the CNAME is correctly set and traffic is being served to your VibeSite.
Propagation usually completes within the TTL window (about 1 hour), but can take up to 48 hours to fully propagate across the internet. Keep checking the status in MultiHub.

Troubleshooting
“Can’t edit” or “Can’t delete” on existing records: This is normal for the A records and NS records. You don’t need to touch those. Just add the new CNAME record.
A rentnow or www CNAME already exists: Confirm that the existing domain is the correct record (Eg. site-acacia-park-apts.pages.dev). If not, update the existing record to match.
Error saving the record: Some DNS providers can be flaky. Wait a moment and try again. If it persists, try refreshing the page.