I have 4 Netlify sites on the same domain—1 on the primary, 3 on subdomains—and I received emails saying that automatic renewal of the SSL cert for all had failed.
When I try renewing manually through the Netlify admin I consistently get a “[domain] doesn’t appear to be served by Netlify” message.
I use external DNS. These sites have been running on Netlify for years and there have been no recent DNS changes.
In reviewing the DNS settings I saw that I was pointing to possibly outdated values for the CNAMES (netlify.com instead of 'netlify.app`) and that Netlify now seemed to use a new load balance IP for the A record. I updated those yesterday. Today I’m still getting the message that Netlify doesn’t think it’s serving these sites. Everything looks propagated and no issues shown on letsdebug.net
When I look at the domains tab for your account, I see another domain listed (as registered externally) but not parsnip.io. This being the case, I think the first thing to try is to remove the custom domain here…:
and add it back again. Would you mind giving that a shot and letting is know how it goes?
Thanks for looking at it! I removed the custom domain from the site and added it back but it didn’t appear to resolve it. It still says “parsnip.io doesn’t appear to be served by Netlify” and shows the certificate expiring in 4 days. The “Renew Certificate” button no longer shows.
In most conditions, we can provision certificates no matter who is hosting DNS; I can’t tell what was happening with your site when you wrote in, only that our internal DNS lookups failed to show that we hosted the site even back on 2 Sep, is why that banner is/was showing in the UI.
Perhaps you had some “AAAA” records configured already, that weren’t pointing to Netlify? (there is no AAAA record that you can use that points to Netlify, and when this happens, our UI isn’t always the best at informing you that we saw it.)