Read the delegation
The parent zone's NS set is the routing instruction resolvers encounter first.
Direct answer: A nameserver lookup returns the domain's published NS hostnames and resolves the IPv4 and IPv6 addresses currently associated with each authoritative server name.
The server resolves the domain's NS records and then resolves each returned nameserver hostname to public addresses. Result responses are private, uncached and excluded from search indexing. Do not enter passwords or secrets. Read the lookup privacy policy.
What this nameserver lookup tells you
Nameserver lookup focuses on delegation: the servers published to answer authoritatively for a domain and the addresses needed to reach them. It helps diagnose registrar-to-DNS-provider handoffs without conflating them with web hosting.
- Which NS names are visible for the domain
- Which IPv4 and IPv6 addresses those server names resolve to
- Whether further parent-versus-child comparison is needed
If these servers are part of a provider change, work through the nameserver migration checklist before editing the registrar delegation.
To distinguish parent delegation, child authority and required glue, use the parent-and-child delegation guide.
How the evidence is collected
Resolve server addresses
In-bailiwick server names may need parent glue to avoid a circular lookup.
Query every authority
A strong diagnosis asks each listed server for SOA and compares authority, serial and child NS data.
Read the fields without overclaiming
| Signal | What it can establish | What it does not prove |
|---|---|---|
| Parent NS | Delegation published by the parent zone. | A guarantee the server hosts the zone. |
| Child NS | NS set served from inside the zone. | The routing data caches necessarily used first. |
| Glue | Parent-supplied addresses needed to reach in-bailiwick servers. | A replacement for authoritative A/AAAA data. |
| SOA serial | A value operators use to coordinate zone versions. | A universal timestamp format. |
Parent and child NS sets differ after migration
A short overlap can appear during a controlled change, but persistent mismatch complicates caching and troubleshooting. Verify the registrar delegation, ask every old and new server directly, and keep the old provider serving the correct zone until relevant caches have expired.
Common mistakes
- Calling nameservers the website host
- Checking only the child NS set
- Ignoring unreachable IPv6 glue
- Taking equal serial numbers as proof that every record matches
Nameserver Lookup FAQ
How many nameservers are required?
Policy varies, but operational resilience generally requires multiple authoritative servers with independent reachability.
What is a lame delegation?
The parent points to a server that does not answer authoritatively for the delegated zone.
Can I change nameservers here?
No. This is read-only. Delegation changes are made through the registrar or registry channel responsible for the domain.
Explore more nameserver lookup and domain research questions