A Name Server (NS) Record is a fundamental type of DNS record that specifies which DNS server is authoritative for a particular domain. It essentially tells the internet where to go when someone tries to access your domain. Without accurate NS records, your website, email services, and other domain-related functions may not work correctly. When a user types your domain into a browser, an NS record directs that query to the correct DNS server, which then provides other relevant records like A, MX, or CNAME to complete the request. For example, an NS record for example.com might point to ns1.vergecloud.com and ns2.vergecloud.com. These nameservers handle all requests related to example.com, ensuring that visitors can access your website reliably.
VergeCloud provides updated NS addresses for domains using its DNS and CDN services. These nameservers are optimized for speed, reliability, and global availability. However, in some scenarios, certain NS addresses may not be fully compatible with all domain registrars or configurations. In such cases, you can switch to alternative NS addresses that use common top-level domains (TLDs) like .com or .net. Doing so helps maintain smooth domain resolution and ensures your DNS setup meets registrar requirements.
https://api.vergecloud.com/docs#tag/domain/put/v1domainsdomainns-keys
curl --location --request PUT 'https://api.vergecloud.com/domains/example.com/ns-keys' \ --header 'Authorization: Bearer API_KEY' \ --header 'Content-Type: application/json' \ --data '{"ns_keys":["ns1.example.com","ns2.example.com"]}'
A Glue Record is a DNS record that provides the IP address of a nameserver when that nameserver is part of the domain it serves. Glue records are essential to prevent circular dependencies in DNS resolution. For example, if ns1.example.com is the authoritative nameserver for example.com, the system needs to know the IP address of ns1.example.com to resolve the domain correctly. Without a glue record, DNS queries could get stuck in a loop.
After setting custom NS records in VergeCloud, the system assigns IP addresses to the new nameservers. You must then copy these IPs and register them as Glue Records with your domain registrar. Skipping this step is a common cause of domain resolution failures, so it’s important to complete it accurately.
After configuring custom NS and registering Glue Records, you should verify the setup to ensure everything works as expected. The dig command is a reliable tool for this purpose:
dig NS example.com
; <<>> DiG 9.16.1-Ubuntu <<>> NS example.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56473 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 1 ;; QUESTION SECTION: ;example.com. IN NS ;; ANSWER SECTION: example.com. 86400 IN NS ns1.example.com. example.com. 86400 IN NS ns2.example.com. ;; Query time: 58 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Thu ;; MSG SIZE rcvd: 114