IDN domain with ñ (entredueños.com / xn--entredueos-n6a.com) stuck on Pending DNS verification - DNS not propagating

Support
1

Hi Netlify community,

We are experiencing a DNS propagation issue with our IDN domain that contains the Spanish character ñ.

Netlify site name: entreduenos.netlify.app

Account: Entre_Duenos (entreduenos1 at gmail)

Domain situation:

  • entreduenos.com - Working fine (Netlify DNS active)
    • www.entreduenos.com - Working fine
    • entreduenos.com with ñ (Punycode: xn--entredueos-n6a.com) - Pending DNS verification (stuck)
      DNS records in GoDaddy for the IDN domain:
  • A record: @ pointing to 75.2.60.5 (Netlify load balancer IP, TTL 600s) - already set
    • CNAME: www pointing to entreduenos.netlify.app (TTL 600s)
  • Recommended: ALIAS/ANAME to apex-loadbalancer.netlify.com
    • Fallback: A record to 75.2.60.5 - THIS IS ALREADY SET
      The problem:
      The A record pointing @ to 75.2.60.5 is already correctly configured in GoDaddy, but Netlify still shows “Pending DNS verification” for the Punycode version. The DNS record has been in place for several days and is not resolving.

We believe this may be a bug in how Netlify handles IDN domains containing special characters like ñ during DNS verification.

Questions:

  1. Is there a known issue with IDN domain verification for domains containing ñ or other non-ASCII characters?
    1. Can Netlify verify xn--entredueos-n6a.com given that the A record already points to 75.2.60.5?
    1. Is there any workaround to manually trigger DNS verification for this IDN domain?
      Thank you!
2

Update after 12+ hours: The issue persists. The domain xn--entredueos-n6a.com (entredueños.com with ñ) still shows “Pending DNS verification” in Netlify despite the A record pointing to 75.2.60.5 being correctly set in GoDaddy for over 12 hours.

We verified with external DNS lookup tools that the A record IS resolving correctly to 75.2.60.5 worldwide, but Netlify’s verification system is not recognizing it.

This strongly suggests the issue is on Netlify’s side — specifically, a bug or limitation in how the DNS verification system handles IDN/Punycode domains (xn-- prefix). The standard ASCII domain entreduenos.com works perfectly with Netlify DNS, but the IDN version is stuck.

Could a Netlify staff member please look into this? We need this escalated as the domain has been unresolvable for several days.

4

Hey @entreduenos-cars :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!