This is the third article in our series about Custom Domains.

It is intended to give you some best practices for managing your Custom Domain, to avoid potential errors that could impact access or site security.
​
If you have a paid account and have yet to set up a Custom Domain for your site, please refer to this article to get started: Can I Use a Custom Domain for My MV Site
​
​For help troubleshooting the Custom Domain process, you can refer to this helpful guide: Custom Domain Troubleshooting Guide
​
Now we'll take a look at four common scenarios you may encounter regarding custom domains, with tips on how to best handle them.

When you move to a new domain host you need to migrate the CNAME records.

If the CNAME records are not in place, the domain can't be validated and it will appear that the site is disconnected.
​
Here's an example of CNAME records in a domain hosted by SquareSpace.

CNAME records will usually be found under "DNS Records", "Domain Settings", or something similar.

Each hosting service has a different Admin panel, so you will need to locate the CNAME records for your specific host.

NOTE: before attempting to create new CNAME records in a new domain host, make sure to copy and paste your existing records into a text document for backup.

Domain validation and your site security certificate (SSL) depend on your domain name having a few critical records in place.
​
When one CNAME record gets deleted (the first one usually) then the domain can't be validated.

This will show an error or simply a blank page that doesn't load when you enter your custom domain URL.
​
Another problem that CNAME records may lead to is a warning that the visitor is entering a "non-secure site".

This means the SSL certificate could not be produced, which the browser interprets as an illegitimate website.
​
This problem can be difficult to trace because SSL certificates renew every 90 days.

If you have changed your CNAME records within the past 90 days, you may have inadvertently created a site security error.
​
To avoid this problem, maintain your CNAME records (usually the first one).
​
If you are experiencing a site security error, it is possible that one of your CNAME records was altered or changed several weeks in the past.
​
You can rectify this by reviewing your correct CNAME records in your MV admin.

Compare them to the records in your domain host, and ensure that the correct records are in place.

Losing access to your Domain could happen when a hosting plan expires, or when you lose access to a recovery email address that is connected to your domain hosting service.

Resolving this may require getting in touch with the person who first setup your DNS hosting service.

Make sure that your hosting plan is paid & active, or that the contact email address in your domain host is up to date.

When changing custom domains, it is important to be thorough in completing all the steps of the process.

As above, a missing CNAME record can disconnect your site and leave your visitors unable to access your wonderful MV content.

Any time you change custom domains, be sure to visit your domain host to delete your existing CNAME records and enter the new CNAME records for the new custom domain you wish to use.

If your initial attempt to enter CNAME records fails, it will help to get in touch with your domain host and find out exactly what format they require for CNAME records.

Every domain host is different, and some of them do not use all the text characters that MV provides in a CNAME record.

After you have created a Custom Domain, it is critical to be aware of your DNS settings.

Anytime you change domain hosting, move a site, or install extra software services such as firewalls, you MUST factor in your DNS settings as part of your update process.

Best practice: keep a separate log of any DNS changes you make.

Record all URLs, CNAME records, changes, date of change and what you did.

This will be incredibly helpful in the future if you encounter any problems.

It's important that you are able to restore anything that gets corrupted -- especially your DNS records.

​Questions? Reach out to us at hello@membervault.co, within our Facebook group, The MV Collaborative, or via chat support within your admin account (not sure how to log in? look up your account here).