Do also note the addresses are not netlify.com but .netlify.app
Have you added the domain to Netlify DNS? You only add a domain (under https://app.netlify.com/teams/<TEAM-NAME>/dns) if you are using Netlify DNS. Currently mitchmalone.design uses Porkbun DNS not Netlify DNS. If you wish to use Netlify DNS and not Porkbun, check out Delegate your domain to Netlify | Netlify Docs
And the reason you are seeing this message
is because of the inaccurate domain configuration outlined above.
I agree with everything @jasiqli said (thank you!) and I would add that if you do choose to use external DNS, you’ll want to delete the inactive DNS zone here as that has been known to cause problems with SSL cert provisioning. To learn more about inactive DNS zone check out this support guide here.
I updated the NS values to the Netlify values AFAIK. Do I need to update the CNAME? I didn’t see any instructions for that, except for a subdomain but that doesn’t apply to me I think.
Have you added the domain to Netlify DNS?
I’m not sure. I think? I’m not sure what “delegate” means here. I followed the instructions in the link you sent (AFAIK!) and now I’m in this situation. I updated the NS records in my domain registrar (Porkbun) to with the Netlify values…does that mean I’m delegating the domain to Netlify?
Should I just delete the DNS zone thingys in Netlify? Do I need to change the NS settings in Porkbun?
whois shows mitchmalone.design is still using Porkbun DNS
% whois mitchmalone.design | grep -i 'name server'
Name Server: curitiba.ns.porkbun.com
Name Server: salvador.ns.porkbun.com
Name Server: fortaleza.ns.porkbun.com
Name Server: maceio.ns.porkbun.com
as does a dig trace
% dig mitchmalone.design +trace | tail -n 6
;; Received 707 bytes from 2001:dcd:3::10#53(c.nic.design) in 14 ms
mitchmalone.design. 52 IN A 184.108.40.206
mitchmalone.design. 52 IN A 220.127.116.11
;; Received 79 bytes from 18.104.22.168#53(curitiba.ns.porkbun.com) in 16 ms
Changing nameservers from Porkbun to another DNS host will usually break any Porkbun-hosted services such as web hosting and email. Make sure your new DNS host is set up to answer requests for these services before you change nameservers.
Looking back at the screenshot you posted, it seems Porkbun isn’t hosting email but forwarding it (based on the MX record fwd1.porkbun.com.) So yes, there is a possibility this might break. Before delegating to Netlify you would configure all necessary records. See
The simplest option then to remain using Porkbun DNS and follow the Configure external DNS for a custom domain which keeps DNS in Porkbun and requires you to only set up two records: one for the apex mitchmalone.design and one for the subdomain www.mitchmalone.design.
This way no impact to email or any other services set up in Porkbun will occur.