OAuth DNS Endpoint fleet-auth.prd.na.vn.cloud.tesla.com Returning NXDOMAIN Globally

[Jaywatts]

Issue Summary
Since early July, DNS resolution for the Tesla Fleet API OAuth endpoint fleet-auth.prd.na.vn.cloud.tesla.com has consistently returned NXDOMAIN across major public resolvers including Google, Cloudflare, and Quad9. This disruption is preventing OAuth login flows from completing, affecting integrations that rely on token refresh—such as Home Assistant, TeslaMate, and custom API clients.
What I've Observed
DNS resolution fails globally across all tested resolvers
curl requests confirm the domain is unreachable
Redirect URIs, client ID, and scopes are compliant with Tesla’s documentation
The OAuth login flow halts before redirect, resulting in broken authentication for dependent services
This appears to be a backend infrastructure issue rather than a misconfiguration.
There’s no mention of endpoint deprecation or migration on Tesla’s Fleet API Announcements
Very little discussion in GitHub repos, Tesla forums, or HA community threads
EU endpoint (fleet-auth.prd.eu.vn.cloud.tesla.com) resolves, but returns 401 Unauthorized for North America–based accounts
Questions
Has Tesla silently migrated or deprecated this NA endpoint?
Is there an alternative hostname or fallback strategy for NA-based OAuth clients?
Has anyone received clarification from Tesla Dev Support?
Any updates or confirmation from other devs would be greatly appreciated. This feels like a platform-level outage or transition that deserves wider visibility.
Thanks in advance!

[Bre77]

I'll ensure the library is using https://fleet-auth.prd.vn.cloud.tesla.com/oauth2/v3/authorize because Tesla did announce that as a higher rate limit endpoint, but didn't say anything specific about the old endpoints.