NS Records Updated but Traffic Not Routing Through VergeCloud
Common Issues After Changing Nameservers to VergeCloud
First Reason: Delay in Change Implementation
You may have updated your NS records, but the changes have not yet taken effect.
.com Domains
For domains ending in .com, changes are typically implemented instantly; however, due to the TTL associated with your NS records, your NS may continue to display the previous name server until the records expire.
To verify the status of your NS records, you can visit www.whatsmydns.net and enter your domain name to check the NS status globally.
Second Reason: Inactive Cloud Service
Your NS changes might be applied, but your cloud service is not activated in the panel. The cloud icon in the panel allows you to enable or disable it in the DNS settings as needed, determining whether your website traffic will pass through VergeCloud.
Important Notes
- Propagation Time: After changing the nameservers, it may take some time for the updates to propagate across DNS servers globally. Domains with
.com or .org TLDs typically update within 5 hours, while other TLD domains may take up to 48 hours. - Pending NS Change Status: If, after updating the nameservers, you see "pending NS change" instead of an active status in the VergeCloud User Panel under the Cloud DNS Product Dashboard, it indicates that the nameservers have not yet been updated across all DNS servers worldwide. This process usually requires some time. To verify whether the nameserver records for your website have been updated globally, you can use the
dig or nslookup commands, or check with tools like DNS Checker and WhatsMyDNS.net. Once the nameserver records are fully updated, your website will automatically change to active status.
Related Articles
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 ...
Troubleshooting DNS_PROBE_FINISHED_NXDOMAIN Error on VergeCloud
Understanding DNS_PROBE_FINISHED_NXDOMAIN Error The DNS_PROBE_FINISHED_NXDOMAIN error occurs when a DNS lookup is performed for a domain name, but no corresponding IP address is found. NXDOMAIN stands for "Non-Existent Domain," indicating that the ...
Troubleshooting ISP Accessibility Issues with VergeCloud CDN.
Resolving ISP Access Issues with VergeCloud If your website is inaccessible to users from specific Internet Service Providers (ISPs) while using VergeCloud's CDN, this guide provides solutions to common causes, such as firewall and rate-limiting ...
Troubleshooting SSL Errors on VergeCloud CDN.
Troubleshooting SSL Errors on VergeCloud If users encounter SSL errors while visiting your website and you are utilizing VergeCloud’s content delivery network (CDN), the issue may stem from several potential causes. This guide outlines common factors ...
Resolving iOS Inaccessibility Issues with VergeCloud CDN
Ignore "upgrade" Header If your website becomes inaccessible to iOS users (e.g., on iPhones or iPads) after integrating VergeCloud CDN, you can resolve the issue by adjusting the Page Rules in your VergeCloud User Panel. Follow the steps below: ...