Have you read the guide above: [Support Guide] What you can do about this error message: “A DNS zone for this domain already exists on NS1” (netlify.com)?
Hey @luke @sid.m I’m having the same issue with richarmstrong.net. I purchased the domain with DreamHost and they don’t use NS1. Is there a phantom on your side?
Appreciate the help!
Hi, as linked above can you reach out to NS1 and ask them to remove this domain from their parking zone. This should be resolved once this is done.
Hey @SamO I tried that. They said to contact Netlify support.
@SamO resolved—not sure by who. Thank you for the support.
Hi @luke
I have the same issue, but it is not scenario you describe. I registered domain UltimateFinanceGuide.com less than 50 hours ago, and it has zero domain history (it didn’t exist before). As soon I registered it, I set Netlify NS for it, and then wen to to Netlify console to configure, and this happened.
I cannot use CNAME at GoDaddy: it will make settings non-standard (I have few other domains using Netlify NS). Also, CNAME at GoDaddy doesn’t support non-WWW primary domain name; and it does not support automatic “Let’s Encrypt”. So, no way, I don’t want to use any workaround; there is the issue, either at NS1 or at Netlify which has to be fixed sooner or later, fixed forever.
Something went wrong between changing NS at GoDaddy and starting configuring DNS with Netlify.
Yes, DNS zone already exist at NS1, but it is zone I created two days ago, “I own it”, otherwise if I follow “Managed DNS 161” link change at GoDaddy will remove “zone” at NS1 (otherwise, it is bug in NS1).
Please fix it; error message even says “we will escalate this on your behalf to NS1”.
Thanks,
You set the name servers before adding the domain to Netlify DNS @FuadEfendi? You need to do the opposite: Add the domain to Netlify DNS, configure the name servers provided.
There a two different Netlify DNS configurations in existence for ultimatefinanceguide.com @FuadEfendi
$ whois ultimatefinanceguide.com | egrep '^Name Server'
Name Server: DNS1.P01.NSONE.NET
Name Server: DNS2.P01.NSONE.NET
Name Server: DNS3.P01.NSONE.NET
Name Server: DNS4.P01.NSONE.NET
Name Server: DNS1.P03.NSONE.NET
Name Server: DNS2.P03.NSONE.NET
Name Server: DNS3.P03.NSONE.NET
Name Server: DNS4.P03.NSONE.NET
Only one of these should exist. The correct values are those provided when you added the domain to Netlify DNS. Remove the other values.
Yes, I set it before; copy-pasted settings for p01, then p03, then even tried both from another already configured server. And I can see now from Network Tools: DNS,IP,Email that I had to use dns1.p09.nsone.net - dns4.p09.nsone.net instead; I was suspecting this too.
I hope this will be the fix.
But then we need to add it to docs, “use only settings which Console suggests, don’t be in a rush”.
UPDATE:
I deleted, reconfigured,…
Please check this again, yellow exclamation marks, issues at NS1:
- second way has big cons for me: you cannot use non-WWW as a primary domain with GoDaddy, you cannot use “Let’s Encrypt”, and you are forced to use different tools & consoles (I have few domains already configured with Netlify).
Anyway, I do not know what correct values are right now; I set it to
➜ t-gpt git:(main) ✗ whois ultimatefinanceguide.com | egrep ‘^Name Server’
Name Server: DNS1.P09.NSONE.NET
Name Server: DNS2.P09.NSONE.NET
Name Server: DNS3.P09.NSONE.NET
I found these magic names by querying Network Tools: DNS,IP,Email
“Netlify Console” doesn’t shows which one I should use right now (after I made mistake)
That is the incorrect way of doing things.
I don’t believe this. Show me where it says this.
Remove the domain from Netlify DNS. Set the name servers back to the default GoDaddy servers. Start the process of adding the domain to Netlify DNS again following the Netlify DNS documentation.
???
Are you in a role of SME, trying to help newbies?
You can not use A record type (non-WWW) pointing to abcd-xyz.netlify.com; only to IP address (which hosts millions sites). A record should point to IP address of Netlify. And CNAME WWW pointing to example-com.netlify.com.
Anyway, this
So that, you cannot configure “example.com” to be your primary domain if it is hosted by Netlify and NS is at GoDaddy.
You cannot use CDN, and many other things, and I simply don’t like using “www” with static sites having zero dependency on anything else (on subdomains for example)
Regarding your other suggestions, yes, I tried; deleted completely from Netlify, reset GoDaddy to default Name Servers, tested that NS1 does not have any zone anymore (associated to my domain); started process again; same issue. Support team says “maybe someone set zone at NS1” and referred to this forum post - very naive support, to be politically correct.
I hope in 24 hours issue will disappear. Or maybe after some power outage 
I leave you in the hands of Netlify Support now @FuadEfendi.
Hi there! I’m going to escalate you to the Help Desk so we can assist you there! Thanks!
Hello, the same issue here, my domain was bought from godaddy and I’, getting the attached error, could you help please?
Hi @mateussisto 
thanks for reaching out! I have escalated your query to our helpdesk. we will follow up with you via email on ticket #296880
1 Like
Hello Everyone,
I have been struggling to set DNS for my domain broganboots.com .I have failed after multiple attempts every tried deleting any dns zone that exist for my domian from bigrock .Please help and guide for the some. Thank you already! Cheers!! 
The reason for this error (“A DNS zone for this domain already exists on NS1”) is one of two things. Either some other company has already configured a DNS zone for this domain at NS1 or a zone has previously existed on Netlify. In either of these cases, a new zone cannot be created. We are not the only company that builds our services using NS1 as a component. For example, Squarespace also uses NS1, so if you’ve configured this domain at Squarespace (or a similar service) that will prevent us from doing the same.
There are two solutions for this.
- Fastest & Easiest Solution: Set up external DNS by creating an A and CNAME record following the attached guide. This will unblock you immediately.
- If you’ve used the domain with a different service, you’ll need to contact that service to have them remove the configuration for this domain at NS1. NS1 won’t tell us who the other company is that already configured this domain with their service. This means you will need to determine which other services you have used for DNS service for this domain and contact that company to get this removed.
We hope this helps! Please let us know if you have any follow-up questions.
1 Like
Hello My dear friend,
Thank you for getting back to me. Please refer the screenshots attached there is no ns1 record for the existing domain still I am struggling to point my domain to netlify. The domain buyer has confirmed there is no ns1 record. Please
check things from your end. Thanks Already !
Did you try this? Are you unable to do it?