How do I connect a custom domain?
Use your own domain name (like yourwedding.com) instead of the default wedsites.com subdomain for a more personalized website address.
Short answer: Go to Settings, enter your domain in the Custom domain (optional) field, then update your DNS settings with the provided records.
Requirements
A domain name purchased from a registrar (GoDaddy, Namecheap, Google Domains, etc.)
Access to your domain's DNS settings
A WedSites account on any paid plan (custom domains are not available on the free trial)
Setting up your custom domain
Go to Settings
Find the Custom domain (optional) field
Enter your custom domain (e.g., ourwedding.com)
Click Save
You'll see DNS records to add to your domain registrar
Adding DNS records
Log into your domain registrar and add these records:
A record (for your main domain like ourwedding.com):
- Type: A
- Name: @ (or leave blank, depending on registrar)
- Value: 37.16.10.26
- There should be only one A record for @. Delete any others.
CNAME record (for www subdomain like www.ourwedding.com):
- Type: CNAME
- Name: www
- Value: domains.wedsites.com
Best practice (recommended): Add both the A record and CNAME record so both your apex domain and www subdomain work.
Waiting for DNS propagation
DNS changes can take 15 minutes to 48 hours to fully propagate
You can check progress by visiting your custom domain
SSL certificates are automatically provisioned once DNS is configured
Important: Remove conflicting A records
Before adding new DNS records, check if your domain already has A records for @ (your apex domain). Many registrars set up default A records for parking pages or built-in website builders. If you leave these in place alongside the WedSites A record, your site will only work some of the time — visitors will randomly get sent to the wrong address.
Delete any existing A records for @ that don't point to 37.16.10.26. If your registrar has a built-in website builder or parking page service, you may need to disable it first before you can remove its records.
Tips
Don't use "Forward with masking" - this causes security warnings
Both www and non-www versions will work once configured
Keep your wedsites.com subdomain active as a backup
If you see "Not Secure" warnings, wait for SSL certificate provisioning
Make sure you only have one A record for @ — multiple A records cause intermittent loading issues
Related articles