Summary
The 'primary name server not listed at parent' error in MXToolbox, when using Squarespace, generally arises from a mismatch between the nameservers configured at your domain registrar (Squarespace) and those defined in the DNS zone file. The solutions revolve around verifying and correcting these records, ensuring consistency and accuracy. DNS propagation delays of up to 48 hours are common and can temporarily cause this error. Glue records are critical if your nameservers are subdomains of your main domain, requiring careful attention. Further, double-checking the SOA record, using DNS lookup tools, and ensuring A records point to the correct location can aid in identifying and resolving discrepancies. If troubleshooting doesn't work, contacting Squarespace support is recommended.
Key findings
- DNS Record Mismatch: The fundamental cause is inconsistencies between nameserver settings at Squarespace and in the DNS zone file.
- Propagation Time: DNS updates need time (up to 48 hours) to propagate across the internet.
- Glue Record Importance: Glue records are essential when nameservers are subdomains, ensuring proper delegation.
- SOA Record Significance: The SOA (Start of Authority) record must align with the configured nameservers.
Key considerations
- Record Verification: Carefully double-check nameserver records, SOA records, and A records for typos or inaccuracies.
- Use DNS Tools: Employ online DNS lookup tools (like MXToolbox) to confirm record accuracy and propagation.
- Squarespace Support: Contact Squarespace support if the issue persists despite thorough troubleshooting.
- Correct Registrar Settings: Make sure to correct the nameserver and glue record settings at the registrar (Squarespace).
What email marketers say
9 marketer opinions
The 'primary name server not listed at parent' error on MXToolbox when using Squarespace indicates a mismatch between the nameserver records at your domain registrar (Squarespace) and the DNS zone file. Common solutions involve verifying and correcting these records, ensuring they match. DNS propagation delays can temporarily cause this error, so waiting up to 48 hours is advisable. Glue records are critical if your nameservers are subdomains of your main domain. Checking the SOA record and using DNS lookup tools can help identify discrepancies. Contacting Squarespace support is recommended if you're unable to resolve the issue yourself.
Key opinions
- DNS Mismatch: The root cause is typically a mismatch between the nameservers configured at Squarespace and those in the DNS zone file.
- Propagation Delay: DNS changes can take up to 48 hours to propagate, so patience is required.
- Glue Records: Ensure glue records are correctly set up at Squarespace if your nameservers are subdomains.
- SOA Record: Verify that the Start of Authority (SOA) record matches the configured nameservers.
Key considerations
- Double-Check Settings: Thoroughly check all nameserver records and ensure there are no typos.
- Use DNS Tools: Utilize online DNS lookup tools to verify your DNS records are correct.
- Squarespace Support: If troubleshooting steps don't resolve the issue, contact Squarespace support for assistance.
- Check External DNS: Ensure any external DNS services you might be using are correctly configured to delegate authority to your Squarespace DNS.
Marketer view
Email marketer from StackOverflow recommends using online DNS lookup tools (like MXToolbox itself) to check the authoritative nameservers for the domain and comparing them with the settings in Squarespace. They advise ensuring there are no typos in the nameserver entries.
2 Apr 2025 - StackOverflow
Marketer view
Marketer from Email Geeks shares a link to Digital Ocean documentation about fixing the "Primary Name Server not listed at parent" DNS error.
28 Dec 2024 - Email Geeks
What the experts say
2 expert opinions
Experts highlight that the 'primary name server not listed at parent' error stems from inconsistencies between registrar settings and DNS zone files. A crucial step is to review and align these settings meticulously, with specific attention to glue records for nameservers hosted within the domain and confirming A records and name servers are correctly pointing to the proper locations and resolving.
Key opinions
- Inconsistent DNS: The error arises from mismatches between settings at the domain registrar and the DNS zone file.
- Glue Record Importance: Careful attention to glue records is necessary when nameservers are hosted within the domain.
- A Records: Ensure A records are correctly pointing to the proper locations and are resolving.
Key considerations
- Settings Alignment: Thoroughly review both registrar and DNS zone file settings, ensuring they are synchronized.
- Record Verification: Verify A records and name servers are pointed correctly and resolving.
Expert view
Expert from Word to the Wise says it is important to check that any A records are pointing to the correct location and the nameservers are correct when you get a DNS error. Checking these records and ensuring they are resolving can help address the issue.
24 Oct 2023 - Word to the Wise
Expert view
Expert from Spam Resource emphasizes that DNS configuration issues, like the 'primary name server not listed at parent' error, arise from inconsistencies between registrar settings and DNS zone files. They recommend carefully reviewing and aligning both settings, paying close attention to glue records for nameservers hosted within the domain.
17 Feb 2025 - Spam Resource
What the documentation says
3 technical articles
Official documentation explains that resolving the 'primary name server not listed at parent' error involves ensuring the nameservers configured at the domain registrar (Squarespace) match those defined in the DNS zone file. Squarespace documentation details how to point a domain to an external site by editing DNS settings, while Google Domains Help specifies that glue records are necessary when the nameserver is a subdomain of the domain.
Key findings
- Nameserver Mismatch: The error signifies a discrepancy between the nameservers at the registrar and in the DNS zone file.
- Squarespace DNS Editing: Squarespace provides instructions for modifying DNS settings to point the domain externally.
- Glue Records Essential: Glue records are required when using a subdomain as a nameserver.
Key considerations
- Verify Nameservers: Carefully check and correct the nameserver records at both the registrar and DNS provider.
- External Site Setup: If pointing to an external site, follow Squarespace's guidelines for DNS editing.
- Subdomain Nameservers: When using a subdomain for the nameserver, ensure glue records are properly configured in Google Domains (if applicable).
Technical article
Documentation from Squarespace Help explains that to fix the issue, you need to point your Squarespace domain to an external site by editing DNS settings. This involves deleting the default records and adding custom records provided by your website provider.
10 Oct 2021 - Squarespace Help
Technical article
Documentation from Google Domains Help explains that a glue record is needed when your nameserver is a subdomain of your domain. This can be added via the Google Domains interface.
13 Feb 2022 - Google Domains Help
Are custom sending domains worth the money and effort?
How do I fix the MXtoolbox SPF record DNS lookup limit exceeded error?
How do I properly set up SPF and DKIM records for email marketing, including handling multiple SPF records, IP ranges, bounce capturing, and Google Postmaster Tools verification?
How do I set up SPF and DKIM records for new subdomains when using third-party email services?
How do SPF, DKIM, and DMARC email authentication standards work?
What are best practices and costs for implementing DKIM, SPF, and DMARC?
