I think the issue was that the custom domain was added to the site before the Netlify DNS zone existed. I say this because the NETLIFY/NETLIFYv6 records required do exist now. These records are only created when the custom domain is added to the site.
Those records exist now and are much newer than this conversation about this custom domain. It was adding them to the new site that created the required DNS records.
The other solution for this would have been to remove the custom domain from the previous site settings and to add it back again. This would have also triggered the creation of the required DNS records.
If there are other questions about this, please let us know.
hi @jillztom - yes, that is possible, which is why we don’t allow folks to delete them through the UI. If you immediately replace the record, you can keep any possible downtime as short as possible. For most customers, this is acceptable, but if you have a special case let us know.
I have a locked subdomain that’s not served in Netlify. I want to remove it from the Netlify DNS since it’s an important subdomain. The record name is [delivery.coffeeorcode.com] and my site name is romantic-neumann-8f7a7c.netlify.app .
I appreciate you so much. I’m facing another issue and have been for some time now. I have a domain purchased through godaddy but I transferred it to Netlify and everything was working perfectly fine. But then someone on my team did something they shouldn’t have. They tried to use our domain for firebase custom hosting . this broke everything and now the site is down. The screenshot below is what I see when I visit domain settings (it’s been more than 24 hours and the nameserver values exist in godaddy), I’m not sure if you can provide some assistance on this?
Note, there are no NETLIFY or NETLIFYv6 type records to unlock at this time for this custom domain.
Important note: The DNS zone above isn’t being used by your domain at this time.
It is an inactive DNS zone and we have a support guide about how to correct this issue here:
Note, you don’t have to use Netlify DNS to host your site with a custom domain at Netlify. You can also use the DNS at the registrar and use the external DNS instructions instead.(In other words, using Netlify DNS is optional.) Please use whichever solution you prefer and if there are questions about either solution, please let us know.
hi, @luke I am creating a new DNS record with the A record for my domain name but while creating it is raising the error “dns_api workpeer.in - workpeer.in/A: 400 - link exists, all config must be empty”. Although we didn’t have any A record type. Could please help why this error keep raising. For your understanding,