| Warning |
|---|
You have tried to access an archived page. Please go to the new https://root360.atlassian.net/wiki/spaces/KB to find more documents. |
...
If you want to point a second-level domain name, e.g. "example.com" to your root360 environment, you cannot simply point an A record to a public IP of your root360 environment. Root360 environments are accessed through elastic loadbalancers that do not have stable IPs. Instead, they have stable domain names which point to a set of changing IPs to enable cross-availability-zone redundancy.
...
There are now two problems. If example.com is set as CNAME to the AWS load balancer, mail is no longer working. If example.com is set as an A-Record to one of the loadbalancer IPs, AWS may change the IP of their loadbalancer at any time an the DNS entry will be obsolete.
The solution is:
For www.example.com, set a CNAME with the domain name of the loadbalancer
Redirect example.com using our root360 redirect service by pointing it to an A record to our redirect service. The service will then redirect any http(s) requests to www.example.com
(Optional) always fully-qualified domains
Features 
Redirect any domain example.com to www.example.com for HTTP. HTTPS works automatically because we provide a SSL certificate using letsencrypt (AWS SSL Certificates issued by Amazon are unfortunately not available).
Specific redirections from subdomains to the directory structure eg specialties.feinkost.de after www.feinkost.de/spezialitäten . This configuration requires configuration by root360.
| Warning |
|---|
Letsencrypt certificates will be refused by the default browsers in Android devices using Android <7.1.1 beginning in January 11, 2021. For more information see the announcement about the changes of letsencrypts root certificate. |
...