[Support Guide] What you can do about this error message: "A DNS zone for this domain already exists on NS1"

Support Support Guides
,
28

I am trying to connect my domain “example.space” to my Netlify site, but I am encountering an issue. Previously, I made a mistake by entering “example.com” instead of “example.space” when setting up the domain on Netlify. I then tried to correct this by removing “example.com” and adding “example.space,” but I received the error message: “A DNS zone for this domain already exists on NS1.”

To resolve this, I have removed the Netlify nameservers (dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net) from my domain settings at my registrar, Porkbun.

Could you please remove the existing DNS zone for “example.space” from your system so that I can set it up again correctly? I believe this will allow me to reconnect my domain properly.

29

I’ve routed your request to our helpdesk, we’ll follow up via email.

30

Great, the sooner the better. Thanks.

34

please help

“I deleted my DNS zone for rhumbamusictv.com, but I’m still seeing the error ‘A DNS zone for this domain already exists on NS1’ when trying to re-add it. Please clear the old zone from NS1.”

35

Subject: DNS Zone Conflict Error (“A DNS zone for this domain already exists on NS1”)

Hello Netlify Support Team,

I am receiving the error “A DNS zone for this domain already exists on NS1” when trying to set up my custom domain, 2-a-h.com, on a new Netlify site.

Context:

  1. This domain was previously working fine with another Netlify site under my account.
  2. I deleted the old site and the custom domain from the Netlify dashboard.
  3. I am now trying to attach 2-a-h.com to my new site (site name TBD, or provide the Netlify app URL if known).
  4. The error persists, indicating a “phantom” or “parked” zone still exists on NS1 from the previous configuration, blocking the creation of the new zone.

Goal:
I need the existing, conflicting DNS zone for 2-a-h.com to be manually cleared from your NS1 backend so I can use Netlify DNS for this domain.

For now alternative (Temporary Solution):
I have temporarily set up the domain using External DNS (keeping OVH Nameservers and using Netlify’s A Record) to keep the site running, but I would prefer to use Netlify DNS for management consistency.

Could you please assist in initiating a zone clearance request with NS1?

Thank you for your help.

37

This explanation is really helpful, especially for site owners who run into this error without realizing the domain may have been previously connected to another platform using NS1. The step-by-step breakdown of options makes it much clearer what to try next instead of guessing.

For sites like CapCut APK that focus on downloads and content delivery, having DNS set up correctly is critical to avoid downtime or SSL issues. Knowing that using external DNS is a valid and performant fallback is reassuring, and it’s good to see that contacting Support to clear the zone is still an option when Netlify DNS is preferred.

Thanks for documenting this so clearly—it saves a lot of time during setup and migrations. as explained in this support guide.

39

Support Request: DNS zone already exists on NS1 for htps://www.google.com/search?q=onseacademy.com. I have added the verified-for-netlify TXT record to prove ownership of htps://www.google.com/search?q=onseacademy.com. Can you please purge the existing DNS zone so I can add it to my account?