Site says Awaiting Netlify DNS

Support
1
  • Site name: refold-core.netlify.app
  • Domain: app.refold.la

Note: if you try the first url, you should get a 404 which means the site is up. All app capabilities are on dark links.

  • Did you try Ask Netlify, our generative AI chatbot, before posting?
    Yes, it just gave me generic answers

I re-launched an app that had been turned off. When it relaunched, it was accessible at the netlify domain, but not at its friendly subdomain.

Looking through the forums, I found a post instructing me to remove all records to it and then recreate it through the site settings, which would create a Netlify record.

I deleted a CNAME record, and the Netlify record. Also removed it from the app. Then I readded it as a Domain Alias in the Production domains section of the app settings. This recreated the Netlify record (but not the cname). However, the settings still say “Awaiting Netlify DNS”. It’s been like that for 4 days.

I"m not 100% sure what the Netlify record actually does. Do I also need to create a new CNAME record?

Thanks.

3

Hi, @Refold. None of the changes you are making using Netlify DNS are going to make any difference because the domain is not using Netlify DNS in any way:

refold.la.		21600	IN	NS	jule.ns.cloudflare.com.
refold.la.		21600	IN	NS	kevin.ns.cloudflare.com.

If you want to use Netlify DNS, you will need to stop using Cloudflare for DNS. However, as the apex domain refold.la is successfully using Cloudflare, you probably do not want to use Netlify DNS.

Instead, you probably should either:

A) create the DNS records in Cloudflare following these instructions: Configure external DNS for a custom domain | Netlify Docs

or:

B) Configure Cloudflare to proxy that domain to Netlify

Which to do (A or B above) is up to you. Please note, with either solution above this inactive DNS zone must be deleted:

https://app.netlify.com/account/dns/refold.la

The only reason to keep that DNS zone around is if you do plan to move the domain to using Netlify DNS. As it is not using it now, that is an “inactive DNS zone”. Inactive DNS zone are neither recommended nor supported. We strongly recommend deleting inactive DNS zones as they often cause issues as covered here:

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