A domain could fail to resolve because the name server changes did not completely propagate, DNSSEC or the domain registrar needs verification, the DigitalOcean name servers are not configured at your registrar, or there are different name server providers active.
How do I fix the DNS error "Primary Name Server Not Listed at Parent"?
Last verified 11 Nov 2026
The “Primary Name Server Not Listed at Parent” error occurs when the primary name server in your domain’s Start of Authority (SOA) record does not match any of the name servers configured at your domain registrar. DNS checkers compare the primary name server in the SOA record with the name servers listed at the parent domain’s registry.
For domains using DigitalOcean’s authoritative DNS service, the SOA record typically lists ns1.digitalocean.com as the primary name server. To resolve this error, update your domain registrar to use all three DigitalOcean name servers: ns1.digitalocean.com, ns2.digitalocean.com, and ns3.digitalocean.com.
If you have configured vanity/branded name servers pointing at DigitalOcean’s name server IP addresses, read Why aren’t my vanity DNS name servers resolving?.
Related Topics
If you use vanity or branded DNS name servers that delegate to DigitalOcean’s name servers, point their A, AAAA, and glue records at DigitalOcean’s current name server IPs.
Use the app’s Settings tab to remove domains associated with App Platform apps.