DNS Records Cloud Option

After migrating your website to VergeCloud and completing your DNS configurations, you can view and manage the A Records of your domain and its subdomains under the DNS Records section in the CDN settings of your user dashboard.

What is the Cloud Option?

The Cloud Option is a feature that allows you to enhance your website’s performance and security by routing traffic through VergeCloud’s CDN edge servers. When the cloud option is enabled, your domain’s traffic, as well as that of its subdomains, is directed through VergeCloud’s global CDN infrastructure. If it is disabled, the traffic flows directly to your domain without CDN acceleration.

Benefits of Enabling the Cloud Option

Activating the cloud option enables several powerful features, including:

• Caching: Improved caching of static content, reducing latency for end users.
• Web Acceleration: Enhanced performance due to optimized routing and CDN-based acceleration.
• Security Features: Activation of security measures, such as DDoS protection and Web Application Firewall (WAF), to safeguard your website.
• Traffic Logs: Access to detailed analytics and traffic logs for your domain and subdomains.

Enabling the Cloud Option via API

You can also enable the cloud option for your DNS records using VergeCloud’s API. Below is an example API request that enables the cloud option for a specific record:

curl --location --request PUT 'https://api.vergecloud.com/domains/example.com/dns-records/Record_ID/cloud' \
--header 'Authorization: Bearer API_KEY' \
--header 'Content-Type: application/json' \
--data '{"cloud":true}'

Technical Considerations

• The VergeCloud CDN service is applicable only for HTTP and HTTPS protocols, specifically on ports 80 and 443.
• When the cloud option is enabled and traffic is being routed through VergeCloud's CDN edge servers, there is no restriction on upload volume. However, note that the HTTP request headers must not exceed 16 KB in size, and the maximum interval between consecutive writes should be 180 seconds.
• If the Web Application Firewall (WAF) is active, the maximum permissible body size for an HTTP request is 524,288 bytes (512 KB).
• VergeCloud CDN allows the following ports for end-user connections: 80, 8080, 8880, 2052, 2082, 2086, 2095, 443, 2053, 2083, 2087, 2096, and 8443. VergeCloud can also connect to your origin server using any port over HTTP or HTTPS.

Services Not Recommended for Cloud Option Activation

It is important to note that enabling the cloud option for A Records associated with certain services can lead to service disruptions. Specifically, non-HTTP services such as email or FTP should not have the cloud option enabled. If such services are mistakenly routed through the CDN, they may become inaccessible or behave unexpectedly.

To turn off the cloud option for specific records, navigate to the DNS Records section and click on the cloud icon next to the service you wish to exclude.

Services That Should Not Have an Active Cloud Option

• autodiscover
• calendar
• chat
• cPanel
• cvs
• e
• email
• exchange
• ftp
• game
• gameserver
• git
• google
• imap
• irc
• local
• localhost
• mail
• mobilemail
• mx
• panel
• pda
• pop
• repo
• secure
• sftp
• sites
• smtp
• ssh
• ssl
• stream
• streaming
• svn
• vid
• video
• vids
• vpn
• webmail
• webstats

Testing Cloud Option Activation

Once you have activated the cloud option, you can verify the status of your DNS records by using the dig command:

dig A example.com

Sample Test Output

; <<>> DiG 9.16.1-Ubuntu <<>> A example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 67890
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;example.com.                   IN      A

;; ANSWER SECTION:
example.com.            3600    IN      A       203.0.113.20

;; Query time: 35 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Sep 26 14:45:12 UTC 2024
;; MSG SIZE  rcvd: 68

Considerations for Testing

• Ensure that the A record points to the correct IP address associated with VergeCloud’s CDN when the cloud option is enabled.
• Allow up to 48 hours for DNS changes to propagate globally before testing.