After you create or import your application into Cloud Platform, you can access each of your application’s environments using its default domain name. An environment’s default domain name is based on its application name (or sitename) and realm (for example, the domain name for a Production environment could be examplesite.devcloud.acquia-sites.com). You should then configure a DNS domain name for the Production environment, such as www.example.com, and configure DNS records using the information located at the top of your Domains page.
The default acquia-sites.com domain name provided with your subscription has the following limitations:
acquia-sites.com domain unless it is explicitly listed under the DNS section of your Domains page.acquia-sites.com domain can’t be changed or removed.acquia-sites.com domains to an environment.robots.txt file.acsitefactory.com instead of acquia-sites.com.acquia-sites.com domain.To view the domain information for an environment, go to the Applications > [Environment] > Domains page, and then scroll to the DNS information card.
The DNS information card displays the CNAMEs and IPv4 addresses (A records). You must configure DNS settings for your domains.
After an environment is created, Cloud Platform provisions the environment with a custom Cloud Platform subdomain with a name ending in acquia-sites.com. For limits on these default domain names, see Limitations on default domain names.
After you add a custom domain name to an environment, the Cloud Platform can route incoming requests for that domain name to the environment selected. You must then configure your DNS settings with your DNS provider to ensure all requests for that domain are routed to Cloud Platform.
The Cloud Platform supports IPv6 in certain infrastructure configurations. DNS endpoints listed on the Domains page with ‘dualstack’ at the beginning are IPv6 compatible. Please contact Acquia Support if your organization requires IPv6 support and your environment does not currently support it.
To add a domain to one of your application’s environments:
On the Domains page for the environment into which you want to add a domain, click Add Domain in the upper right.
The Add a domain dialog box appears.
In the Domain to add field, enter the domain name without the protocol header. For example, use mysite.com instead of http://mysite.com.
If you want to make your application available to multiple related domain names (such as example.com and www.example.com), individually add each domain name. Otherwise, you can use the wildcard character ( * ) in a single domain entry to allow for subdomains.
Subscribers with many domains may have several pages of domain names displayed on their Domains page. You can either use the pager to browse for a domain, or use the Filter field to search.
By default, the domain name you use must be composed of Latin-based characters. If you have a domain that uses non-Latin characters, you can use Punycode to convert these characters into values recognized by standard DNS.
After converting your characters with Punycode and using them with your domain name in place of the non-Latin characters, you should be able to configure your DNS entries normally.
You can determine whether your domain name is properly resolving to your Cloud Platform website by clicking click the Status link for the domain on the Applications > [Environment] > Domains page. Acquia performs a DNS lookup for your domain name and displays one of the following status messages:
If your domain name doesn’t resolve to your Acquia application, or if it doesn’t resolve at all, ensure you have followed the instructions in Configuring DNS records for your application.
Cloud Platform can’t determine the status of wildcard (*) domains; it disables the Status link for these domains.
To remove a domain from an environment:
Each domain name associated with your account has its own Varnish cache to speed page access.
If your application supports Varnish caching, clearing these caches ensures that anonymous website visitors get the most up-to-date version of your application after you make any changes.
To clear the Varnish cache for a domain name, click the Clear Caches link for the domain. For more information, see Using Varnish.
Applications that use the default domain name ending in acquia-sites.com are not intended to be publicly available. Therefore, Cloud Classic uses a robots.txt file to disallow crawling of those domains by search engine robots. Robots that reach your application using your DNS domain name, such as www.example.com, operate normally. These robots can crawl your application for searches. Note that the robots.txt file does not necessarily prevent content indexing or content inclusion in the search results of acquia-sites.com domains. For more information, see Limitations on default domain names and robots.txt.
*.acquia-sites.comacquia-sites.com domain is listed under DNS on the Domains page, or you are an Site Factory subscriber, pointing your CNAME to an acquia-sites.com domain can make your application load inefficiently, and can cause unpredictable results or even downtime during platform maintenance activities.If this content did not answer your questions, try searching or contacting our support team for further assistance.
The default acquia-sites.com domain name provided with your subscription has the following limitations:
acquia-sites.com domain unless it is explicitly listed under the DNS section of your Domains page.acquia-sites.com domain can’t be changed or removed.acquia-sites.com domains to an environment.robots.txt file.acsitefactory.com instead of acquia-sites.com.acquia-sites.com domain.*.acquia-sites.com domains.acquia-sites.com domain is listed under DNS on the Domains page, or you are an Site Factory subscriber, pointing your CNAME to an acquia-sites.com domain can make your application load inefficiently, and can cause unpredictable results or even downtime during platform maintenance activities.To view the domain information for an environment, go to the Applications > [Environment] > Domains page, and then scroll to the DNS information card.
The DNS information card displays the CNAMEs and IPv4 addresses (A records). You must configure DNS settings for your domains.
After an environment is created, Cloud Platform provisions the environment with a custom Cloud Platform subdomain with a name ending in acquia-sites.com. For limits on these default domain names, see Limitations on default domain names.
After you add a custom domain name to an environment, the Cloud Platform can route incoming requests for that domain name to the environment selected. You must then configure your DNS settings with your DNS provider to ensure all requests for that domain are routed to Cloud Platform.
The Cloud Platform supports IPv6 in certain infrastructure configurations. DNS endpoints listed on the Domains page with ‘dualstack’ at the beginning are IPv6 compatible. Please contact Acquia Support if your organization requires IPv6 support and your environment does not currently support it.
To add a domain to one of your application’s environments:
On the Domains page for the environment into which you want to add a domain, click Add Domain in the upper right.
The Add a domain dialog box appears.
In the Domain to add field, enter the domain name without the protocol header. For example, use mysite.com instead of http://mysite.com.
If you want to make your application available to multiple related domain names (such as example.com and www.example.com), individually add each domain name. Otherwise, you can use the wildcard character ( * ) in a single domain entry to allow for subdomains.
Subscribers with many domains may have several pages of domain names displayed on their Domains page. You can either use the pager to browse for a domain, or use the Filter field to search.
By default, the domain name you use must be composed of Latin-based characters. If you have a domain that uses non-Latin characters, you can use Punycode to convert these characters into values recognized by standard DNS.
After converting your characters with Punycode and using them with your domain name in place of the non-Latin characters, you should be able to configure your DNS entries normally.
You can determine whether your domain name is properly resolving to your Cloud Platform website by clicking click the Status link for the domain on the Applications > [Environment] > Domains page. Acquia performs a DNS lookup for your domain name and displays one of the following status messages:
If your domain name doesn’t resolve to your Acquia application, or if it doesn’t resolve at all, ensure you have followed the instructions in Configuring DNS records for your application.
Cloud Platform can’t determine the status of wildcard (*) domains; it disables the Status link for these domains.
To remove a domain from an environment:
Each domain name associated with your account has its own Varnish cache to speed page access.
If your application supports Varnish caching, clearing these caches ensures that anonymous website visitors get the most up-to-date version of your application after you make any changes.
To clear the Varnish cache for a domain name, click the Clear Caches link for the domain. For more information, see Using Varnish.
Applications that use the default domain name ending in acquia-sites.com are not intended to be publicly available. Therefore, Cloud Classic uses a robots.txt file to disallow crawling of those domains by search engine robots. Robots that reach your application using your DNS domain name, such as www.example.com, operate normally. These robots can crawl your application for searches. Note that the robots.txt file does not necessarily prevent content indexing or content inclusion in the search results of acquia-sites.com domains. For more information, see Limitations on default domain names and robots.txt.
If this content did not answer your questions, try searching or contacting our support team for further assistance.