The following article outlines how to customise the URL on many of your Arlo hosted pages from "<platformname>.arlo.co" to e.g. training.mycompany.com, or www.mycompany.com.
This is a technical process and the instructions in this article are written for an IT Specialist. Arlo has no control over your hosting and domain setup and cannot assist with your initial domain configuration or CNAME records.
Arlo allows you to white label many of your Arlo hosted pages, the customer portal and the checkout with your own domain.
When using the customer portal, once you set up a custom domain, administrators will no longer be automatically logged in and will end their session on the management platform if they log into the customer portal and vice versa.
For customers where the whole website is hosted by Arlo (i.e. Arlo website) this will generally be all pages with event information pulled from Arlo as well as the checkout pages.
For customers using our WordPress plugin, Web Controls, or custom API options, the pages hosted by Arlo are generally only the checkout pages and the customer portal.
There is a one-off setup fee which you can find under the optional extra services. If you would like to purchase a custom domain please contact your Customer Success Manager.
As custom domain configuration is a multi-step process, custom domain configuration time frames may vary. Please allow up to 10 days for the setup process.
SSL protection is essential for all platforms, including those on custom domains. The default Arlo SSL certificate cannot be used with custom domains, as this certificate applies only to *.arlo.co addresses.
Before we can make a domain name change for you, we will need to obtain a SSL certificate for your custom domain. This is free of charge.
Please request an SSL certificate along with your request to Arlo to update the hosted pages to your custom domain.
The following process describes how to set up a custom URL for your website. The setup is a two-step process that involves the configuration (and verification) of the DNS CNAME record, and then the second stage is us reconfiguring your platform to use this new DNS.
If the domain you would like Arlo to use is currently hosting another website, please do not make any DNS changes yet. Doing so would break your current website. Instead, please indicate in your email to Arlo Support that you have an existing website that you would like to migrate to Arlo Website. We will guide you through the correct sequence of steps to prevent any downtime for your website.
- Ask your IT staff to add a DNS entry for the domain you would like Arlo to use. They need to create a CNAME DNS record pointing at the arlo.co domain for your platform.
- The required format for this entry is:
<subdomain>.mycompany.com IN CNAME <your-platform-name>.arlo.co
- For example:
training.fcbgroup.com.au IN CNAME fcbgroup.arlo.co
Arlo does not support dual domain names on a single platform, meaning you cannot create two subdomains that point to Arlo.
If you own a second domain and wish it to point to your Arlo pages, we recommend you set up a redirect from this domain to your Arlo pages' domain. Most DNS hosts support domain redirects like this. If your DNS host doesn't support this, you should be able to point that domain on your own web server and perform a redirect there.
Once your IT team has created the CNAME record in your DNS, send an email to your Customer Success Manager Important: Do not use the new CNAME on your site yet.
Please include the following
- Your platform name (will be in the current url <platformname>.arlo.co)
- The new URL you wish the Arlo pages to use
- A request for Arlo to obtain an SSL certificate through our hosting provider (AWS)
- If you want your Arlo website to be available on the bare domain as well as the subdomain, please let us know when requesting the SSL certificate
Our team will work with your IT team to obtain and validate the SSL certificate.
Note: It may take up to 7 - 10 business days to process the custom domain request. We'll let you know when the new domain will be active (you should allow a day after the change is made).
If you want your Arlo website to be available on the bare domain as well as the subdomain (e.g. mycompany.com as well as www.mycompany.com), you will need to set up a redirect service.
Because CNAME records are not allowed on the domain root (mycompany.com), the method listed above will not work to make your Arlo website available on your domain root. Instead, you will need to set up a redirect service that will respond to web requests directed at https://mycompany.com/ and redirect those requests to https://www.mycompany.com/.
How to configure a redirect service will vary according to your website provider.
If a redirect is not configured, anyone trying to use the domain root URL to get to your site will not see your Arlo hosted pages.
- Clear your browser's cache or view the page on another computer to see if the problem still exits. If it does still exist, see below.
- If you have no www. at the start of the web address, add the www. If you're now directed to the new website, see the below instructions.
Domain root not directing to new site
If you're entering the web address without the www. (entering a bare domain, e.g. mycompany.com) and you are not seeing the new site, you will need to add a redirect on the domain root so that anyone entering the bare domain will be redirected to the Arlo hosted pages (e.g. www.mycompany.com). Learn more about adding a redirect.
If you can't access the Arlo hosted pages from your workplace, but you can access them away from that network (e.g. at home), your organisation's network may have been set up to block access to certain websites.
Ask your IT team if they have a split-brain DNS set up for the root domain on your intranet. A setup like this is not uncommon for internal corporate networks (particularly those using Windows Active Directory), but it does affect how staff inside the network access certain websites.
If your corporate DNS is set up this way, your IT team will need to add a specific A record entry to your internal DNS server(s) for your subdomain.