NS Records Updated but Traffic Not Routing Through VergeCloud

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.