To activate VergeCloud services, you first need to replace your domain's Name Servers (NSs) with VergeCloud's NSs at your registrar. If you’re using CNAME-based traffic forwarding, you must add or update the DNS record linked with VergeCloud in your current DNS service.
You can utilize the nslookup tool to check the NS status of your domain. For instance, the NSs of the example domain vergecloud.com are displayed in the nslookup output below:
nslookup vergecloud.site
Server: 8.8.4.4
Address: 8.8.4.4#53
Non-authoritative answer:
Name: vergecloud.site
Address: 31.57.157.100
Name: vergecloud.site
Address: 31.57.158.100
This tool not only shows the NS status but also displays the DNS record status for the domain. You can also check the NS status using the dig
command.
dig vergecloud.site
; <<>> DiG 9.10.6 <<>> vergecloud.site
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34778
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;vergecloud.site. IN A
;; ANSWER SECTION:
vergecloud.site. 64 IN A 31.57.157.100
vergecloud.site. 64 IN A 31.57.158.100
;; Query time: 54 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Apr 23 16:42:08 IST 2025
;; MSG SIZE rcvd: 75
The root (@) DNS record refers to the primary domain. This record should be an A, ANAME, or AAAA type record.
To route incoming traffic through VergeCloud's edge servers for enhanced security and acceleration before it reaches your origin server, you should activate the cloud icon for this record.
An example of a root A record (@) with an active cloud icon can be seen below:
When the cloud icon is enabled, your server IPs remain hidden, and VergeCloud IPs are displayed.
dig globalartworks.in
; <<>> DiG 9.10.6 <<>> globalartworks.in
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 444
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;globalartworks.in. IN A
;; ANSWER SECTION:
globalartworks.in. 180 IN A 31.57.158.100
globalartworks.in. 180 IN A 31.57.157.100
;; Query time: 87 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Apr 23 16:47:29 IST 2025
;; MSG SIZE rcvd: 78
With the cloud icon disabled, the DNS returns the original domain IPs, which could pose potential security risks:
dig globalartworks.in
; <<>> DiG 9.10.6 <<>> globalartworks.in
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33523
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;globalartworks.in. IN A
;; ANSWER SECTION:
globalartworks.in. 120 IN A 1.2.3.4
;; Query time: 133 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Apr 23 16:44:52 IST 2025
;; MSG SIZE rcvd: 62
As seen in the example image, the IP displayed is the same one entered in the VergeCloud panel as the primary IP of our server.
This record points to your www subdomain and can be of type A, ANAME, CNAME, or AAAA.
The Smart Checker steps for this record are similar to those for the root (@) record. Additionally, you can specify the desired configuration for this record in your domain’s dashboard:
dig www.globalartworks.in
; <<>> DiG 9.10.6 <<>> www.globalartworks.in
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43304
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.globalartworks.in. IN A
;; ANSWER SECTION:
www.globalartworks.in. 180 IN A 31.57.157.100
www.globalartworks.in. 180 IN A 31.57.158.100
;; Query time: 70 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Apr 23 16:32:47 IST 2025
;; MSG SIZE rcvd: 82
If you are using a mail server on your primary domain, setting up an MX record is essential. Ensure the record name corresponds to the appropriate subdomain.
To secure the connection between users and VergeCloud edge servers, enabling the SSL certificate in VergeCloud’s settings is required. You can configure your domain’s HTTPS policies in the HTTPS settings section.
VergeCloud automatically requests and activates a free SSL certificate for your domain using DNS Authentication.
Enabling the cloud icon for your domain's DNS records allows VergeCloud to act as a reverse proxy, providing added security, performance optimization, and content delivery efficiency for your website.
To confirm your configurations are working correctly, you can use various command-line tools and browser checks:
nslookup
followed by your domain name to verify NS records.dig
for detailed DNS record status, particularly for verifying the root and www DNS records.curl
with the HTTPS URL to check SSL functionality and ensure the CDN is delivering the content as expected.Below is a sample curl
command to add a DNS record through the VergeCloud API:
curl -X POST "https://api.vergecloud.com/v1/dns-records" \
-H "Authorization: Bearer your-api-key" \
-H "Content-Type: application/json" \
-d '{
"type": "A",
"name": "@",
"content": "your-server-ip",
"proxied": true
}'
VergeCloud's CDN Smart Checker is a diagnostic tool designed to help you analyze and verify the configuration of your domain, DNS records, and SSL settings. It ensures optimal traffic flow and identifies potential misconfigurations.
CDN (Content Delivery Network): A globally distributed network of servers that deliver content based on user location and server availability.
NS (Name Server): A DNS record that specifies which server manages your domain’s DNS settings.
DNS (Domain Name System): Translates domain names into IP addresses.
To activate VergeCloud services:
Log in to your domain registrar.
Replace your existing NS records with VergeCloud’s NS records.
Update the relevant DNS record in your current DNS provider to point to VergeCloud.
nslookup vergecloud.com
Output Example:Server: 8.8.4.4 Address: 8.8.4.4#53 Non-authoritative answer: Name: vergecloud.com Address: 31.57.157.100 Name: vergecloud.com Address: 31.57.158.100
Alternatively, use dig
:
dig vergecloud.com
This refers to the primary domain (e.g., example.com
).
Record Types: A, ANAME, or AAAA
Best Practice: Enable the cloud icon to route traffic through VergeCloud’s edge network.
dig globalartworks.in
Result Shows VergeCloud IPs:
globalartworks.in. IN A 31.57.158.100 globalartworks.in. IN A 31.57.157.100
dig globalartworks.in
Result Shows Origin IP:
globalartworks.in. IN A 1.2.3.4
This reveals your actual server IP, which could pose a security risk.
This record handles traffic to www.yourdomain.com
.
Supported Types: A, ANAME, CNAME, AAAA
Setup: Same process as the root record; configure through VergeCloud dashboard.
dig www.globalartworks.in
Expected Output:
www.globalartworks.in. IN A 31.57.157.100 www.globalartworks.in. IN A 31.57.158.100
Enabling the cloud icon ensures VergeCloud proxies your traffic securely.
If you're using email services for your domain, ensure your MX record is configured correctly. This should point to your mail provider’s servers and match the appropriate subdomain.
To secure user communication with your site:
Enable SSL in your VergeCloud dashboard.
VergeCloud automatically generates a free SSL certificate using DNS Authentication.
You can manage HTTPS behavior under the HTTPS Settings section.
Enabling the cloud icon for DNS records:
Activates reverse proxy
Hides your origin IP address
Enables traffic routing through the CDN for better speed and security
Use these tools to verify your configuration:
nslookup: Check NS record resolution
nslookup yourdomain.com
dig: Validate A/CNAME/MX records
dig yourdomain.com
curl: Confirm SSL certificate and HTTPS access
curl -I https://yourdomain.com
Use VergeCloud’s API to add DNS records programmatically:
curl -X POST "https://api.vergecloud.com/v1/dns-records" \ -H "Authorization: Bearer your-api-key" \ -H "Content-Type: application/json" \ -d '{ "type": "A", "name": "@", "content": "your-server-ip", "proxied": true }'