This can happen after you move your website to a new hosting provider, change DNS providers, or update your domain’s name server settings. In some cases, the warning may appear even when your website is working normally.
The important thing is to understand why the error appears before changing your DNS settings. In this guide, we’ll explain what the error means, what causes it, and how to fix it.
What Does “Primary Name Server Not Listed at Parent” Mean?
The “Primary Name Server Not Listed at Parent” error usually means that the primary name server mentioned in your domain’s DNS settings is missing from the list of name servers registered with the parent zone.
To understand why this happens, let’s first look at how DNS works.
The Domain Name System (DNS) helps computers find websites and other online services using domain names like example.com. It follows a hierarchy, so when someone tries to visit a website, DNS helps direct the request to the right name server. For a .com domain, the .com registry points DNS resolvers to the name servers responsible for that domain.
This information is stored in what we call delegation records. These records tell DNS resolvers which name servers to contact when looking up a domain. Your domain also has an SOA (Start of Authority) record. One of its fields, called MNAME, tells us which server is listed as the primary name server for that domain.
If this server isn't listed in the parent zone's delegation records, a DNS checker may show the “Primary Name Server Not Listed at Parent” error. For example, your SOA record might list ns1.oldprovider.com as the primary name server, while your domain's parent zone points to ns1.newprovider.com and ns2.newprovider.com. A DNS checker may flag this difference.
However, this doesn't always mean something is wrong. Some DNS providers use a hidden primary name server that isn't listed in the public delegation records. If that's how your provider works, the warning may be normal and might not need fixing.
What Causes the Primary Name Server Not Listed at Parent Error?
Several issues can trigger this warning. Here are the most common causes.
Your Registrar Has Outdated Name Server Settings
When you switch DNS providers, make sure your domain registrar has the correct name servers. If you miss this step, your domain may still point to your old provider.
This can cause problems if the old name servers are no longer active or don't have the latest DNS records. Your website might stop working, or visitors may get different results depending on which DNS server they reach.
Your SOA Record Points to a Different Primary Name Server
Your SOA record may still name a server that you no longer use. This often happens when DNS settings are copied from an old setup, or someone forgets to update the record during a migration.
Check the MNAME field to see which server is listed as primary. Before changing it, ask your DNS provider to confirm the correct value, as some providers use a hidden primary server by design.
Your Parent and Child DNS Records Do Not Match
Sometimes, the parent zone and your domain's own DNS zone list different name servers. For example, the parent might point to two servers, while your domain's NS records list a different set.
This mismatch can cause DNS checkers to flag your domain. It can also make troubleshooting harder because different servers may return different information. Compare both sets of records to find out where the mismatch starts.
You Recently Changed DNS Providers
After moving to a new DNS provider, you may see this warning even if you've updated your settings correctly. DNS resolvers can keep old information in their cache until its TTL expires.
Check the current records before making any more changes. If the authoritative records are correct but some DNS checkers still show the old information, wait for the cached records to expire and test again.
Your DNS Provider Uses a Hidden Primary Name Server
Some DNS providers manage records on a primary server and then share them with public secondary servers. The primary server may not be listed in the public delegation, even though it appears in your SOA record.
In this case, the warning may be expected. Check your provider's documentation or contact its support team to confirm how its DNS setup works. If the configuration is intentional and DNS is working properly, you may not need to change anything.
How to Fix the Primary Name Server Not Listed at Parent Error
The right fix depends on the cause. Follow these steps to identify the mismatch and correct it without disrupting your website or email.
Step 1: Check Your Domain's Current Name Servers
Start by checking which name servers your registrar has configured for your domain.
- Log in to your domain registrar, such as GoDaddy, Namecheap, or another provider.
- Open your domain management dashboard.
- Find the DNS or name server settings.
- Note the name servers currently configured for the domain.
- Compare them with the name servers provided by your active DNS hosting provider.
For example, your DNS provider may ask you to use: ns1.provider.com and ns2.provider.com. If your registrar still lists name servers from your previous provider, you may have found the problem.
Important: Use the exact name servers supplied by your current DNS provider. Do not copy the example above into your actual configuration.
Step 2: Update the Name Servers at Your Registrar
If the registrar's settings are incorrect, update them to match your active DNS provider.
In most registrar dashboards, you can do this by selecting a custom name server option and replacing the existing entries. Before making the change, confirm that your new DNS provider has the correct records for your website, email, and other services. This includes A, AAAA, CNAME, MX, TXT, and any other records your domain needs.
Once you've checked the configuration:
- Replace the old name servers with the correct ones.
- Remove obsolete entries if your provider instructs you to do so.
- Save the changes.
- Recheck the domain after the update becomes visible.
Do not add extra name servers simply to make the list longer. All listed servers should be part of your intended DNS configuration.
Step 3: Compare the Parent Delegation With Your Authoritative DNS Records
If your registrar's name server settings look correct, the next step is to check what your domain's DNS records actually show. You can do this using Nslookup.io without running commands in a terminal.
Open the tool and enter your domain name to check its NS records. Note the name servers returned in the lookup. Then check your domain's SOA record and look at the MNAME field, which identifies the primary name server.
Compare the primary name server with the name servers listed in the NS lookup. If they don't match, check with your DNS provider to find out whether this is a configuration issue or an intentional setup, such as a hidden primary name server.
Step 4: Check the DNS Configuration At Your Hosting Provider
If the registrar's delegation and the SOA record appear correct, log in to your DNS hosting provider's dashboard.
Check the following:
- The domain is added to the correct DNS zone.
- The zone contains the name servers supplied by the provider.
- The SOA record identifies the intended primary server.
- All authoritative name servers return consistent records.
- The name servers are reachable and responding to DNS queries.
If you've recently migrated your DNS hosting, confirm that the old provider is no longer being used unintentionally. Also, if you manage your own DNS servers, you may need to review the zone configuration and ensure the updated records have been loaded correctly.
For managed DNS services, ask the provider to verify the SOA record and parent delegation if you cannot change these settings yourself.
Step 5: Check for DNS Propagation and Cached Results
If you've already corrected the configuration, give the change some time to become visible. DNS resolvers cache records for different periods based on their TTL (Time to Live) values. As a result, different tools may temporarily show different information.
Wait for the relevant cached records to expire, then run the DNS check again. There is no single propagation time that applies to every DNS change. The registrar's update process, registry behavior, and caching can all affect when the new information becomes visible. If the warning continues, check the authoritative records directly rather than assuming the issue is just propagation.
Step 6: Verify the fix
Once you've made the necessary changes, run your DNS checks again.
Confirm that:
- The parent delegation points to the intended name servers.
- The authoritative name servers publish the expected NS records.
- The SOA record identifies the correct primary server for your DNS setup.
- The authoritative name servers respond consistently.
- Your website and email services continue to work as expected.
You can also use our DNS diagnostic tool to check whether the warning has disappeared.
If the records are consistent but the warning remains, ask your DNS provider whether its architecture uses a hidden primary name server. This can help you distinguish an actual configuration problem from a warning that is specific to your provider's setup.
Final Thoughts
The “Primary Name Server Not Listed at Parent” error usually means the name servers listed in your DNS settings don't match the parent zone. In some cases, it can also happen because your DNS provider uses a hidden primary name server.
Start by checking the name servers at your domain registrar. Then, check your NS and SOA records to find out where the mismatch is coming from.
If you've recently changed DNS providers, make sure your settings are correct and give DNS some time to update. If everything looks fine but the warning persists, contact your DNS provider to confirm whether the setup is intentional.
The main goal is to ensure your DNS settings are correct and that your website and email keep working without issues.