Skip to main content

NS record explained: your domain's nameservers

Published on June 19, 2026 9 min read

An NS record sets which nameservers are responsible for your domain. Learn how delegation works and how to switch your nameservers safely.

Flat illustration of a person beside a signpost with arrows pointing from a globe to a row of identical servers, representing the nameservers responsible for a domain.

An NS record (name server record) sets which nameservers are responsible for your domain. It tells the rest of the internet where the official DNS data for your domain lives. Once you understand how the NS record works, you know exactly what happens when you move to a different hosting or DNS provider, or hand a subdomain over to someone else. This article explains what an NS record is, where it lives, and how to change it safely.

What is an NS record?

NS stands for name server. The NS record is one of the oldest and most important DNS record types, known technically as type 2 and defined in RFC 1035. It points to the hostname of a nameserver, such as ns1.ljpc.network, and effectively says: ask this server for this domain's DNS data.

An NS record always points to a hostname, never directly to an IP address. A resolver (the DNS server that does the lookups on a visitor's behalf) then finds that nameserver's own IP address through its A or AAAA records.

A nameserver is the server that holds and serves a domain's DNS records, such as your A record, MX record, and TXT records. The NS record decides which nameservers are allowed to do that for your domain.

Where NS records live: at the registry and in your own zone

NS records appear in two places, and that distinction is at the heart of how delegation works. Delegation means that responsibility for a domain is handed to a set of nameservers.

The delegation at the registry

At the top sits the registry: the organization that runs your domain's extension. For .nl that is SIDN. The zone for that extension holds NS records that point to your nameservers. This is the delegation: the registry hands responsibility for your domain over to your nameservers.

In practice, these NS records decide where the entire world asks for your DNS. You set them through your registrar, usually in a field called Nameservers. If your domain is registered with LJPc, you do this in the customer portal: open the Domains page in the Services menu, click your domain, and use the Nameservers card. The step-by-step guide is in change your nameservers. Technically these records are not authoritative; they only point to the real source.

The NS records in your own zone

Inside your own DNS zone, at the main domain (the apex), there is a second set of NS records. These are the authoritative NS records: your nameservers confirm for themselves that they are responsible. Most providers add these records automatically. At LJPc, ns1.ljpc.network, ns2.ljpc.network, and ns3.ljpc.network are already in your zone as NS records, both in Plesk and in the customer portal. Leave them in place.

What matters is that both sets agree. If the NS records at the registry point to different servers than the NS records in your zone, you get confusing errors and your domain can become unreliable.

How a domain finds its nameservers

When someone visits your website or sends you email, a resolver runs a short search:

  1. First the resolver asks the root servers. They refer it to the nameservers for the right extension, such as .nl.
  2. The nameservers for that extension use their NS records to say which nameservers are responsible for your domain.
  3. The resolver then asks one of your nameservers and gets the real answer there, such as the IP address from your A record.

This chain of referrals is delegation in action. At every step, the NS record is the signpost to the next stop. Paul Mockapetris designed this tree in 1983 to replace HOSTS.TXT, a single list of every computer on the internet, as described in the history of domain names.

Switching nameservers: moving to another provider

If you want to host your DNS somewhere else, for example because you are moving to a new hosting plan, you change the nameservers at your registrar. Work carefully and in the right order so your domain stays reachable:

  1. First prepare the complete DNS zone at the new provider. Copy over all of your records (A, AAAA, MX, TXT, and the rest) exactly, including those for services outside your hosting, such as an MX record for Microsoft 365 or a TXT record for a verification. If you move to LJPc with a hosting plan, your zone is already set up in Plesk, with the records for your website and email. If your domain is registered with LJPc and you have no hosting plan, click Add DNS hosting on your domain's page in the customer portal and prepare your records there. How to add records is explained in manage DNS records.
  2. Check that all records are correct before you continue. If your new provider already answers for your domain in advance, test that with one of its nameservers, for example dig @ns1.newprovider.com example.com A +short.
  3. Is DNSSEC enabled at your current DNS provider? Then first have the DS record removed there and wait for the TTL to pass: the time a DNS answer may be kept. Otherwise your domain can become unreachable after the switch. How this works is explained in what is DNSSEC. If you change the nameservers of a domain registered with LJPc to another party in the customer portal, we remove the LJPc DS record automatically.
  4. Only then change the nameservers to the new provider's: at your registrar, or in the customer portal if your domain is registered with LJPc. The LJPc nameservers are ns1.ljpc.network, ns2.ljpc.network, and ns3.ljpc.network. In the customer portal, the Switch to LJPc DNS button sets them correctly in one go. If you choose the LJPc nameservers and your domain is registered with LJPc, we then enable DNSSEC automatically.
  5. Keep in mind that the change is not visible everywhere at once. Resolvers keep the old nameservers for as long as the TTL allows. That depends on the delegation at the extension (one hour for .nl, two days for .com) and on the NS records at your old provider. Expect a few hours and sometimes up to 48 hours before everyone uses your new nameservers. More on this in DNS propagation.

Remove the old zone only when you are sure all traffic runs through the new nameservers.

If you also transfer your domain registration to LJPc, your nameservers switch to LJPc automatically when the transfer completes. How that works is explained in transfer your domain to LJPc.

Delegating a subdomain with NS records

You can also use NS records to hand part of your domain to another party or a separate DNS environment. This is called subdomain delegation.

Say status.example.com is run by an external status page. In the zone for example.com you add an NS record for status that points to that service's nameservers. From that point on, that external environment is authoritative for everything under status.example.com, while you keep managing the rest of the domain yourself.

At LJPc, you add such an NS record where you manage your other records: in Plesk with a hosting plan, or in the customer portal if you only have DNS hosting with us. Choose NS as the type, enter the subdomain as the name (for example status), and create a separate record for each of the service's nameservers.

Use subdomain delegation only when you really need it. To point to a single external service, a CNAME record or A record is usually enough.

Glue records and your own nameservers

Sometimes a domain's nameservers sit under that same domain. For example, the nameservers for example.com are called ns1.example.com and ns2.example.com. That creates a chicken-and-egg problem: to look up example.com you need its nameservers, but those live under example.com themselves.

The system solves this with glue records. These are A or AAAA records that the registry supplies alongside the delegation, so a resolver can still find the IP address of those nameservers. You set glue records at your registrar, often under a heading like private nameservers or glue records.

If you use your hosting provider's nameservers, such as ns1.ljpc.network, your domain needs no glue records: those nameservers do not sit under your domain.

Checking NS records

You can look up which nameservers are set for a domain yourself. On macOS or Linux, use dig:

dig NS example.com +short

On Windows, nslookup does the job:

nslookup -type=NS example.com

To see what the extension passes on through the delegation, rather than what your own zone says, use dig with the +trace option. It follows the whole chain from the root servers down to your domain:

dig +trace NS example.com

If the nameservers from both sources match, your delegation is in order. If your domain uses the LJPc nameservers, you see ns1.ljpc.network, ns2.ljpc.network, and ns3.ljpc.network. More ways to test DNS are in troubleshoot DNS problems.

Common problems

Common NS record problems and how to fix them
ProblemCauseFix
Website unreachable after a migrationThe nameservers were switched before the new zone was readyPrepare all records at the new provider first, and change the nameservers only afterward
Change does not seem to take effectResolvers keep the old NS records until the TTL expiresWait up to 48 hours and check with dig in the meantime
Domain returns SERVFAIL or does not resolveThe NS records at the registry and in your zone do not match, a nameserver is not responding, or an old DNSSEC DS record is still in placeMake both sets identical, confirm every nameserver is reachable, and have an old DS record removed
Subdomain does not work after delegationThe NS record points to a hostname without A/AAAA, or to a CNAMEPoint NS to a hostname that has its own A or AAAA records, never to an alias
Domain has only one nameserverIf that one fails, your domain is unreachable. The DNS standard and the customer portal require at least twoAdd at least two nameservers, preferably in separate locations

The NS record is the signpost for your domain: it sets which nameservers do the work and keeps migrations and delegations running smoothly. Still stuck? Contact support and we will be happy to help.

Frequently asked questions

What does an NS record do?

An NS record (name server record) states which nameservers are authoritative for a domain or subdomain. It points to a hostname, not to an IP address.

What is the difference between nameservers and NS records?

Nameservers are the servers themselves that manage your DNS data. NS records are the DNS entries that point to those nameservers. At your registrar you set the nameservers (the delegation), and your zone holds the matching NS records.

How many NS records do I need?

At least two, on separate nameservers, so your domain stays reachable if one goes down. More is allowed and recommended for extra reliability. At LJPc there are three: ns1, ns2, and ns3.ljpc.network.

How long before changed nameservers take effect?

That depends on the TTL. At the extension it is one hour for .nl and two days for .com, and resolvers may also still keep the NS records from your old provider. Expect a few hours and sometimes up to 48 hours before everyone uses the new nameservers.

Can an NS record point to an IP address or a CNAME?

No. An NS record always points to a hostname, and that hostname must have its own A or AAAA records. Pointing to a CNAME (an alias) is not allowed.

Which nameservers do I use with LJPc hosting?

With LJPc hosting you point your domain to ns1.ljpc.network, ns2.ljpc.network, and ns3.ljpc.network. If your domain is registered with LJPc, you set them in the customer portal on your domain's page with the Switch to LJPc DNS button. If your domain is registered elsewhere, you enter them at that registrar in the nameservers field.

Do I need to do anything with DNSSEC when I switch nameservers?

Yes, if DNSSEC is enabled at your current DNS provider. First have the DS record removed there and wait for the TTL to pass before you change the nameservers, otherwise your domain can become unreachable. If your domain is registered with LJPc, we enable DNSSEC automatically after the switch to our nameservers.

Prefer to talk to someone?

We are also happy to answer your questions personally. Schedule a free consultation or call us directly. We are glad to think along with you.

Stay up to date with recent developments! Subscribe and receive our newsletter Signing up...