Cloud Platform
Configuring DNS records for your application
For example, if your application’s bare domain name is example.com and your public IP addresses are 123.123.123.123 and 123.123.123.124, you must configure two A record entries for example.com; one for 123.123.123.123 and another for 123.123.123.124.
Custom domains should not be pointed to any endpoints that are not listed in the DNS section of the Domains page, as this can cause unpredictable results or even downtime during platform maintenance events.
If you have an existing application and decide to upgrade to Shield, both your DNS records and any EIPs assigned to your application infrastructure will change. IP addresses can’t move into or out of a virtual private cloud (VPC).
As a result, when you configure your application in Shield, you must point the DNS records of your application to the new IP address in the VPC. For more information, see Shield.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
For example, if your application’s bare domain name is example.com and your public IP addresses are 123.123.123.123 and 123.123.123.124, you must configure two A record entries for example.com; one for 123.123.123.123 and another for 123.123.123.124.
Custom domains should not be pointed to any endpoints that are not listed in the DNS section of the Domains page, as this can cause unpredictable results or even downtime during platform maintenance events.
If you have an existing application and decide to upgrade to Shield, both your DNS records and any EIPs assigned to your application infrastructure will change. IP addresses can’t move into or out of a virtual private cloud (VPC).
As a result, when you configure your application in Shield, you must point the DNS records of your application to the new IP address in the VPC. For more information, see Shield.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Cloud Platform