Smart Checker

Using VergeCloud's CDN Smart Checker feature, you can assess multiple parameters linked to your service and traffic flow. This feature also notifies you about any potential issues within the domain or its configuration settings. It examines different aspects of the website’s connection, creating a secure and optimal link for the service.

Glossary

• CDN (Content Delivery Network): A system of distributed servers that deliver content to users based on their geographic location, the origin of the webpage, and the content delivery server.
• NS (Name Server): A type of DNS record that indicates which server is authoritative for a domain, directing DNS queries to the correct location.
• DNS (Domain Name System): The hierarchical system that translates human-friendly domain names into IP addresses.

Domain Activation Status

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.com

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

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.com

 

; <<>> DiG 9.10.6 <<>> vergecloud.com

;; 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.com. IN A

 

;; ANSWER SECTION:

vergecloud.com. 64 IN A 31.57.157.100

vergecloud.com. 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

Root DNS Record

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 vergecloud.site  

 

; <<>> DiG 9.10.6 <<>> vergecloud.site

;; 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:

;vergecloud.site. IN A

 

;; ANSWER SECTION:

vergecloud.site. 180 IN A 31.57.158.100

vergecloud.site. 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 vergecloud.site

 

; <<>> DiG 9.10.6 <<>> vergecloud.site

;; 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:

;vergecloud.site. IN A

 

;; ANSWER SECTION:

vergecloud.site. 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.

DNS Record for www

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.vergecloud.site

 

; <<>> DiG 9.10.6 <<>> www.vergecloud.site

;; 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.vergecloud.site. IN A

 

;; ANSWER SECTION:

www.vergecloud.site. 180 IN A 31.57.157.100

www.vergecloud.site. 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

Redirection for the domain occurs only when the cloud icon is enabled, allowing VergeCloud to function as a proxy server.

MX Record

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.

SSL Certificate Activation Status

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.

Cloud Icon Status

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.

Testing and Validation

To confirm your configurations are working correctly, you can use various command-line tools and browser checks:

• nslookup: Run nslookup followed by your domain name to verify NS records.
• dig: Execute dig for detailed DNS record status, particularly for verifying the root and www DNS records.
• curl: Use curl with the HTTPS URL to check SSL functionality and ensure the CDN is delivering the content as expected.