DNS zone not publishing apex A records

Support
,
1

Screenshot 2025-09-25 151800
Screenshot 2025-09-25 1518002319×1122 148 KB

I’m having trouble getting my apex domain (julietiseo.com) to resolve through Netlify DNS, even though delegation and records appear to be correct.

What I’ve done so far

  • Registrar is Porkbun, domain is delegated to Netlify (NS1) nameservers:

    dns1.p01.nsone.net
dns2.p01.nsone.net
dns3.p01.nsone.net
dns4.p01.nsone.net

  • In Netlify DNS, my current records are:

    • julietiseo.com → NETLIFY → julietiseodesign.netlify.app

    • www.julietiseo.com → CNAME → julietiseodesign.netlify.app

    • julietiseo.com → TXT → google-site-verification=…

    • MX records for Google Workspace (ASPMX + ALT1–4)

  • Removed and re-added the apex domain to the site multiple times.

  • Waited >24 hours since switching NS to Netlify DNS.

  • Verified delegation and DNSSEC are correct using DNSViz.

What I’m seeing

  • When I run nslookup ``julietiseo.com, I get only:

    Name: julietiseo.com

    (no IP addresses).

  • DNSViz shows:

    Insecure (1)
julietiseo.com/A (NXDOMAIN)

    Which means Netlify’s nameservers are returning NXDOMAIN for the apex A record.

  • www.julietiseo.com resolves correctly to Netlify via the CNAME.

  • Because the apex isn’t serving A records, Netlify dashboard says “julietiseo.com doesn’t appear to be served by Netlify” and HTTPS certificate provisioning fails.

My question

Is there an issue with the Netlify DNS zone not publishing the apex NETLIFY record to A records (75.2.60.5 / 99.83.190.102)?
Is there anything else I can do on my side, or does this need to be refreshed/reset internally on Netlify’s DNS backend?

Thank you for your help!

2

I believe I’ve run into the same issue described by Luke (Netlify Support Engineer) in this thread. I have worked through Luke’s suggested workflow from my end.

  • Current zone has only:

    • julietiseo.com → NETLIFY

    • www → CNAME → site.netlify.app

    • MX records (Google Workspace)

    • TXT (google-site-verification)

Despite this, julietiseo.com still returns NXDOMAIN for A records (nslookup and DNSViz both confirm), and Netlify will not provision HTTPS.

It sounds like my zone may be in the “stuck” state described in Luke’s reply, and that this needs a manual fix from your side.

Can you please manually refresh/fix the apex NETLIFY record for julietiseo.com so that it publishes the correct A records?

3

The apex domain not resolving and showing NXDOMAIN suggests Netlify’s DNS isn’t properly serving the required A records. Since your setup looks correct, reaching out to Netlify support to investigate and refresh their DNS zone is likely necessary.

5

Hey @kerry :wave:,
Thanks for reaching out!

We’ve gone ahead and created a support ticket for you, so our team can follow up with you directly via email from the help desk. Our Support crew will be in touch with you by email soon.

Great news: these days anyone can reach out to Netlify Support. First, you can try getting an answer using Ask Netlify, our helpful AI search tool. If your question isn’t answered there, you can submit a ticket using the support form, and we’ll take it from there.

We’re keeping the community around for swapping ideas, sharing tips and tricks, and talking shop with other folks building on the platform — but for support issues, tickets are the way to go.

Thanks for being here, and keep an eye out for that email from us!