Site name: upata (upata.com.br)
Domain management shows everything correct: upata.com.br set as primary domain with “Netlify DNS” checked, www.upata.com.br redirecting to primary, SSL cert active for *.upata.com.br, upata.com.br. DNS zone in the dashboard also looks correct - NETLIFY ALIAS record on the apex pointing to upata.netlify.app, added 6 days ago.
However, querying the actual authoritative nameservers directly (both dns1.p08.nsone.net, the domain’s own zone, and dns1.p01.nsone.net, the real authoritative NS for netlify.app itself) for upata.com.br, www.upata.com.br, AND upata.netlify.app all return old AWS IPs (18.208.88.157, 98.84.224.111, TTL 120) instead of Netlify’s own edge IPs. This isn’t a caching issue since I queried the authoritative servers directly.
Can someone take a look at why upata.netlify.app itself is resolving outside Netlify’s infrastructure?