How to Change Name Servers (NS)

How to Change Nameservers (NS)

If you're migrating your DNS management to VergeCloud DNS, you'll need to update your domain's Name Servers (NS records) with your domain registrar (such as GoDaddy, Namecheap, Name.com, etc.).

This guide explains how to update your domain's name servers safely.

Prerequisites

Before updating your name servers, ensure you have:

  • Access to your domain registrar account.
  • The VergeCloud name servers provided to you (for example, delhi.ns.vergedns.com and goa.ns.vergedns.com).
  • All required DNS records already configured in VergeCloud DNS before making the switch.

Update Your Name Servers

The steps vary slightly depending on your domain registrar.

Refer to the appropriate guide below:

  • Namecheap
  • Name.com
  • GoDaddy

Note: If your registrar is not listed above, look for the Nameservers or DNS Management section in your registrar's dashboard and replace the existing name servers with the ones provided by VergeCloud.

If DNSSEC Is Enabled

If your domain currently uses DNSSEC, follow these steps to avoid validation issues during migration:

  1. Remove the existing DS record from your domain registrar (parent zone).
  2. Update your domain's name servers to the VergeCloud name servers.
  3. Enable DNSSEC in the VergeCloud dashboard.
  4. Generate a new DS record in VergeCloud.
  5. Add the new DS record to your registrar to re-enable DNSSEC.

Important: Do not enable the new DS record until the domain is using VergeCloud name servers.

Propagation Time  

After updating your name servers, DNS changes begin propagating across the internet.

  • Initial updates usually start within a few minutes.
  • Global propagation can take 24–48 hours.
You can monitor the propagation status using tools such as DNS Checker or any similar DNS propagation checker.
 

Best Practices

Before updating your name servers:

  • Verify that all required DNS records have been added to VergeCloud DNS.
  • Ensure website, email, and other service records are correctly configured.
  • Keep the old DNS configuration available until propagation is complete.
  • If you're unsure about any DNS records, contact the VergeCloud Support team before switching.

Important Notes

  • During DNS propagation, some users may reach the old DNS while others reach the new DNS. This is normal.
  • If DNS records are missing at the new provider, your website, email, or other services may become temporarily unavailable.
  • If you're using VergeCloud CDN, use only the name servers provided by VergeCloud.

Example

Suppose VergeCloud provides the following name servers:

delhi.ns.vergedns.com
goa.ns.vergedns.com

If you're using Namecheap:

  1. Log in to your Namecheap account.
  2. Open Domain List and select your domain.
  3. Navigate to Nameservers.
  4. Select Custom DNS.
  5. Enter:
    delhi.ns.vergedns.com
    goa.ns.vergedns.com
  6. Click the ✔ Save button.

Your domain will begin using VergeCloud DNS once the changes propagate.

    • Related Articles

    • Using RE2 Regular Expressions

      Using RE2 Regular Expressions Introduction VergeCloud firewall rules support advanced filtering using RE2 regular expressions. These patterns help you match specific text — such as parts of URLs, headers, or query strings — to allow, block, or log ...

    • What is the Cache-Control Header?

      The Cache Control header is one of the most important HTTP response headers used to manage how web content is cached and delivered. It defines how browsers, intermediate proxies, and content delivery networks should store and reuse resources. Proper ...

    • Time to Live (TTL) and DNS Record Configuration in VergeCloud User Panel

      Time to Live (TTL) Time to Live (TTL) is a fundamental parameter in the Domain Name System (DNS) that specifies the duration (in seconds) that a DNS record is allowed to be cached by a recursive resolver. Essentially, TTL determines how long DNS ...

    • VergeCloud Error Codes

      While using VergeCloud services, you may occasionally encounter platform specific error codes. These errors are not random system failures. They usually indicate that a configured rule, security policy, or access restriction has been triggered. This ...

    • Page Rules and Caching Settings for WordPress with VergeCloud CDN

      Setting Up Page Rules and Browser Caching for Your WordPress Site with VergeCloud CDN When you activate VergeCloud CDN for your WordPress site, content is cached on VergeCloud's edge servers for 30 minutes by default. However, some parts of your ...