Troubleshooting Traffic Routing Through VergeCloud CDN: NS Records and Activation

Troubleshooting Traffic Routing Through VergeCloud CDN

After updating your NS records to utilize VergeCloud CDN, you might notice that the traffic isn’t yet routed through VergeCloud. This issue can arise due to two main reasons:

Reason 1: Delay in Propagation of Changes

Although you have updated your NS records, the changes may not take effect immediately.

  • .Com Domains: For domains with a .com extension, the updates typically take effect immediately. However, due to the TTL (Time to Live) value of your NS record, the previous name server may still be in use until the TTL expires.

To confirm if your NS records have been updated, you can visit www.whatsmydns.net, enter your domain name, and check the NS status across different locations globally.

Reason 2: Cloud Not Activated

The changes to your NS records may have been implemented, but the cloud feature is not yet activated. In the user panel, the cloud icon controls whether traffic is passed through VergeCloud. You can enable or disable the cloud icon in the DNS settings, allowing you to choose whether to route traffic through VergeCloud or not.