Summary
The MXToolbox error "primary name server not listed at parent" typically indicates a discrepancy between the name servers your domain registrar has on file and the name servers configured within your domain's DNS records. When this happens, it can prevent proper DNS resolution, affecting services like email delivery and website accessibility. For Squarespace users, this often arises when attempting to point a domain away from Squarespace's default settings or when a custom DNS configuration is misaligned with the registrar's records. This error specifically means that the parent (top-level domain) servers do not recognize the name servers you've set for your domain, which is a critical issue for DNS propagation.
Key findings
- DNS inconsistency: The error signals a mismatch between the name servers recorded at your domain registrar and those in your domain's authoritative DNS zone.
- Propagation issues: Incorrect name server entries prevent DNS changes from propagating globally, leading to service interruptions for your domain.
- Registrar importance: Your domain registrar is the ultimate authority for your name servers. Any changes must be made there to be recognized by the internet's DNS system.
- Email deliverability impact: This error directly impacts your email deliverability because mail servers cannot find your MX records if your name servers are not correctly resolved. For more details on common MX record issues, consider reading our guide on what causes a domain not configured error.
Key considerations
- Verify name servers: Always ensure the name servers listed with your domain registrar precisely match those provided by your hosting provider or Squarespace (if using their DNS). Inconsistent settings can lead to significant deliverability problems. Learn more about DNS changes in our article, why emails fail after switching DNS nameservers.
- Allow propagation time: DNS changes can take 24-48 hours to fully propagate across the internet. Patience is key after making adjustments.
- Consult Squarespace support: If your domain is registered with Squarespace, their support documentation provides specific steps for managing DNS records and nameservers. Refer to the Squarespace guide on troubleshooting third-party domain connections.
- Avoid fragmented DNS: Do not mix name servers from different providers (e.g., Squarespace's name servers and another host's). This is a common cause of this specific error.
What email marketers say
Email marketers often encounter the "primary name server not listed at parent" error when trying to configure domains purchased through website builders like Squarespace, especially when integrating with external email services. Their experiences highlight the challenge of navigating DNS settings that may be simplified or abstracted by the platform, leading to confusion about where exactly to make necessary changes for email deliverability. They emphasize the importance of methodical troubleshooting and direct communication with both the domain registrar (Squarespace, in this case) and the email service provider.
Key opinions
- Registrar is key: Many marketers find that the most crucial step is to ensure the name servers are correctly updated at the domain registrar, even if the primary website is hosted elsewhere.
- Squarespace DNS management: There's a common sentiment that Squarespace's simplified DNS interface can sometimes obscure the full picture of name server configuration, making advanced setups challenging.
- Propagation delays: Frustration often arises from the time it takes for DNS changes to propagate, leading to prolonged troubleshooting periods.
- Impact on email reputation: Marketers recognize that this type of DNS error can severely impact email deliverability and potentially lead to being blocklisted or blacklisted. Understanding how your domain reputation is built and maintained is crucial. Read our guide on recovering domain reputation.
Key considerations
- Confirm DNS setup: Before making changes, confirm whether Squarespace is acting as your domain registrar or just your web host. This dictates where you need to update name servers. Our email deliverability tester can help diagnose these issues.
- Step-by-step guidance: Follow specific instructions from Squarespace's help documentation or your new hosting provider precisely. Do not guess DNS settings.
- Back up current settings: Always record your existing DNS and nameserver settings before making any modifications to facilitate rollback if needed.
- Test thoroughly: After updates, use tools like MXToolbox or other DNS checkers to confirm the error is resolved and that your new configurations (including MX, SPF, DKIM) are correctly propagating. Remember that issues like MXToolbox not showing SPF can stem from underlying DNS problems.
Marketer view
Marketer from Email Geeks explains that the error "primary name server not listed at parent" means your domain's authoritative name servers, which are held by your domain registrar, do not match what the internet's root servers expect. This is a foundational DNS issue that can disrupt everything from website access to email delivery. To resolve this, you must log into your Squarespace account and adjust the name server settings to point to the correct ones provided by your current hosting or email provider. If Squarespace is also your domain registrar, these changes are critical.
Marketer view
Marketer from Netlify Support Forums notes that connecting third-party domains can be tricky due to how different platforms manage DNS. The key is to ensure that your domain registrar, which is Squarespace in this scenario, has the precise name server records that your web host or email service provider requires. Any slight mismatch can lead to resolution failures, preventing traffic from reaching your services. It is essential to double-check every character in the name server entries.
What the experts say
Experts emphasize that the "primary name server not listed at parent" error is a fundamental DNS configuration issue, indicating that the domain's delegation at the top level is incorrect. This means the Internet's authoritative DNS servers cannot properly locate your domain's DNS records, leading to widespread service disruption. They stress the importance of ensuring exact name server entries at the registrar level and understanding DNS propagation mechanics for effective troubleshooting.
Key opinions
- Delegation failure: The error points to a failure in DNS delegation, where the parent zone (the TLD registry) doesn't correctly point to your domain's name servers. This is a critical infrastructure problem for your domain.
- Registrar control: Experts agree that name server changes must always be made at the domain registrar (in this case, Squarespace) to ensure they are propagated to the root DNS servers. Changing them only at the host will not resolve this specific issue.
- DNS health is paramount: Proper DNS configuration is the bedrock of email deliverability. Any misconfiguration at the name server level will prevent any other records (like MX, SPF, or DKIM) from being found, leading to bounces. Our guide to DMARC, SPF, and DKIM highlights their reliance on correct DNS.
- Verify all name servers: Ensure that if your hosting provider gives multiple name servers, all of them are accurately entered at the registrar. Omitting one or having a typo in any can cause the error.
Key considerations
- Check parent zone: The error explicitly mentions the 'parent' zone. This means you must check the name server entries at your domain registrar (Squarespace) first, as that's where the delegation information for the top-level domain (TLD) is managed.
- Understand DNS propagation: Even after corrections, it takes time for DNS changes to update across the internet. Tools like MXToolbox reflect global DNS status, so retesting periodically is necessary. Problems with DMARC propagation, for example, can similarly be affected by DNS delays, as outlined in what causes a DMARC record to not propagate.
- Domain locking: Ensure your domain isn't locked at the registrar level, as this can prevent name server updates from being saved.
- Review all DNS records: Once name servers are corrected, verify all other critical DNS records, such as A, CNAME, MX, SPF, and DKIM. Incorrect DNS records for domain not found errors are common even after nameserver issues are resolved.
Expert view
Expert from Email Geeks indicates that the primary name server error directly impacts the ability of other mail servers to find your domain's MX records, causing email delivery failures. This foundational DNS problem must be resolved first because without proper nameserver resolution, no other DNS records can be looked up. It essentially means your domain is invisible to other mail systems.
Expert view
Expert from SpamResource suggests that DNS health is a primary factor in deliverability. Any issue, especially a critical one like unlisted primary name servers, creates an immediate red flag for receiving mail servers. These errors can lead to temporary rejections, deferrals, or even permanent bounces, severely affecting your sender reputation.
What the documentation says
Official documentation from domain registrars and hosting providers clarifies that the "primary name server not listed at parent" error signifies an incorrect delegation of your domain's authoritative name servers at the registrar level. This is where the global DNS system looks to find out where your domain's specific DNS records are hosted. Documentation from Squarespace specifically outlines the process for users to point their domains to external sites, which often involves modifying these fundamental name server settings.
Key findings
- Root cause: The error occurs when the name servers specified at the domain's parent zone (the registrar) do not match the actual, operational name servers for the domain.
- Registrar's role: Documentation confirms that name server updates must be performed at the domain registrar, as they control the delegation in the top-level domain.
- Squarespace specific steps: Squarespace's own guides provide clear instructions on how to modify DNS settings, including deleting default records and adding custom ones for external services.
- Impact on all services: If name servers are incorrectly listed, neither the website nor email services will resolve, leading to complete service outages for the domain.
Key considerations
- Default nameservers: Squarespace documentation advises checking that you are using their default name servers if the domain is meant to be hosted with them, or explicitly pointing away if moving services.
- URL/IP address requirement: When pointing a Squarespace domain to a non-Squarespace site, you must obtain the correct URL or IP address (and crucially, the nameservers) from your new provider.
- Specific Squarespace menu path: The path to edit DNS in Squarespace is Home menu > Settings > Domains > your domain name > Edit DNS. This specific navigation is key for users to follow.
- Testing connections: Documentation consistently recommends testing connections in a new private or incognito window to verify changes and avoid caching issues after making DNS updates.
Technical article
Documentation from DigitalOcean Support clarifies that the error "Primary Name Server Not Listed at Parent" occurs when the name servers you've provided to your domain registrar are not recognized by the parent zone. This implies a misconfiguration in how your domain is delegated at the highest level of the DNS hierarchy. It is fundamental to the internet's ability to find your domain.
Technical article
Documentation from Squarespace Help Center on troubleshooting third-party domain connections advises users to check with their domain provider (Squarespace) to ensure they are using the correct default name servers, or the specific ones required for third-party hosting. Incorrect name server entries are a primary cause of connection issues.
Related resources
3 resources
Related pages
Why do emails fail after switching DNS nameservers without MX record changes?
What causes a 'domain not configured to use this MX host' bounce message?
What DNS records are required to solve '450 4.1.8 Sender address rejected: Domain not found' errors?
How to troubleshoot MX record issues with Cloudflare when one domain bounces?
What causes a DMARC record to not propagate correctly on GoDaddy?
A simple guide to DMARC, SPF, and DKIM
Why your emails fail at Microsoft: the hidden SPF DNS timeout
Why Your Emails Fail: Expert Guide to Improve Email Deliverability [2025]
