Cannot add an A record

Hi,

I’m getting the following error when trying to add an A record:

dns_api antarapacker.com - antarapacker.com/A: 400 - link exists, all config must be empty

I read in another thread that this can only be fixed by deleting the NETLIFY records, which can only be done by the support team.

Can you please do that for me? Thanks

That would take your netlify site currently served at that address, down. If that’s what you want, please remove the config from the site first (here: https://app.netlify.com/sites/antarapacker-5d4d7/settings/domain#custom-domains), and let us know, and then we’ll get it removed.

If that’s not what you are trying to accomplish, could you please explain your goal so we can give you the best advice?

I’m trying to point my subdomain to my Google App Engine instance. That requires me to add a CNAME record, A records and AAAA records

I do want to keep my netlify website because my domain is pointed to netlify server.

How can I keep both?

Hi, @antarapacker. The NETLIFY/NETLIFYv6 type DNS records will prevent any A, AAAA, and/or CNAME records for the same domain name.

So, if there is an NETLIFY record for example.com then you won’t be able to make CNAME or A record for example.com. (You can make AAAA records for that domain name unless there is a NETLIFYv6 record for it and then they will be prevented also.)

However, if you want to make an A, AAAA, or CNAME record for a subdomain (like www.example.com) that will work as long as no NETLIFY/NETLIFYv6 records exist for that name.

The error at the top of this topic occurs when trying to add an A record for the apex/root domain (antarapacker.com) when a NETLIFY type record also exists for the apex/root domain.

For that apex domain, it is either/or but not both:

  • a NETLIFY type DNS record pointing that apex/root domain to a Netlify site

or:

  • A, AAAA, and/or CNAME records pointing that domain outside of Netlify

Which of these do you want to do?

The error at the top of this topic occurs when trying to add an A record for the apex/root domain ( antarapacker.com ) when a NETLIFY type record also exists for the apex/root domain.

That wasn’t my intention. I wanted to add an A record for subdomain (not root), but looks like you’re right. It’s trying to add an A record to the root domain. Do you know how can I add an A record for subdomain?

For that apex domain, it is either/or but not both:

  • a NETLIFY type DNS record pointing that apex/root domain to a Netlify site

or:

  • A, AAAA, and/or CNAME records pointing that domain outside of Netlify

Which of these do you want to do?

I want to keep NETLIFY type DNS record that is pointing apex/root domain to a Netlify site.

@antarapacker, click the “Add record” button here:

https://app.netlify.com/account/dns/antarapacker.com

Then change the “Name” field from @ to the subdomain you want to add the a record for. ​Does that work?

Please let us know if there are other questions about this.

@luke Looks like I’m running into the same problem.

I am moving my root @ and www over to Webflow, so I need to be able to add A records for them.

I need the NETLIFY and NETLIFYv6 to be moved to just app.addspotlight.com, if that is possible.

I’m okay with the root site going down for a bit, as it’s essential that I move everything over to Webflow asap.

Let me know if there’s anything that I personally need to do to make this happen. Thanks!

Dustin

Hi, @dMcCaffree.

The NETLIFY/NETLIFYv6 records for www.addspotlight.com and addspotlight.com have been deleted. It is now possible to add A records for those domain names.

If there are other questions about this, please let us know.

I am facing the same problem as I have to add cname from namecheap via cloudflare. I had change the setting and realised i cannot point from cloudflare to netlify as it gave an error An A, AAAA or CNAME record already exists with that host. (Code: 81053).

Then I found out this community post so i think I need to get help from support team.

Secondly. If i want to revert back after testing it at some point , what are the steps to be taken as the NETLIFTY records can be only managed by the support team.

The site is down for sometime now. Hope this can be solved asap.
Thanks.

@luke @perry

Can any support team please help? It’s really frustrating that you need to wait to just to change Cname records. The site has been down for a day.

@jen @erez Is it gonna only be resolved in weekdays?

Hi, @newbie. It looks like you have been making many changes and I only can see the changes at Netlify, not the change history at the registrar. Putting together the pieces after the fact I’m left with enough missing pieces of the puzzle that I’m somewhat guessing. However, my best guess is that TTL (time to live) issues were the root cause (but that is only a guess):

There are ways to reduce TTL values and therefore reduce the impact of TTL to DNS changes. There is more about this in the following support guide:

If there are questions about any of this, we are happy to answer.

If you want help planning your DNS changes, we can also help. ​Please let us know what changes you are planning on making and we can give recommendation based on those plans.

Isn’t it because there is NETLIFY records that can only be deleted by support? If not I will wait for 48 hours to see if I can point the cloudflare name server back to netlify for the xxxxxx.netlify.app. Thank you.

What I have done is just changing the name server from netlify to cloudflare on namecheap and now I cannot point the root of the domain on cloudflare to netlify.app subdomain on setting that giving me error. Thanks for your response though.

I know cloudflare cdn is not suggested by netlify but reading from one of the community post about caching and billing, plus the requirement of ezoic. I am trying to put cloudflare in the middle of namecheap and netlify.

I will keep updating

@luke

@newbie, we can make any NETLIFY record deletable for you, which will allow you to point a specific domain somewhere other than Netlify. Let me know which domain(s) you want made deletable and I’ll take care of it.