Nameserver: Where a Domain's DNS Lives
A nameserver is a DNS server that holds and answers queries for a domain's DNS records — where its website points, where its email goes. The nameservers set at the registry delegate authority: when you point a domain at ns1.example-dns.com, you are telling the whole internet which servers speak for that name.
How delegation works
The registry publishes each domain's nameservers in the TLD zone. A resolver looking up your domain asks the TLD's servers, gets referred to your nameservers, and asks them for the actual records. Changing nameservers at your registrar rewrites that delegation — it is the single switch that moves a domain's entire DNS from one provider to another.
What nameservers signal to investors
- •Parking nameservers (e.g. a marketplace's NS) usually mean the name is held for sale, not in active use.
- •A domain on registrar-default nameservers with no records is typically idle.
- •Nameserver changes on a watched domain can signal a sale, a development project, or an expiry-related reset to registrar defaults.
Track your whole domain portfolio in one place
Sourdough is the system of record for domain investors: every domain, renewal date, cost, and sale across all your registrars. 7 days free, then $10/mo. $0 due today.
Frequently Asked Questions
How many nameservers does a domain need?
At least two, by convention and most registries' rules, for redundancy. DNS providers typically assign two to four.
Do nameserver changes affect who owns the domain?
No. Nameservers control where DNS queries are answered, nothing more. Ownership is the registrant record; transfers are a separate registrar-level process.