CDN not working in Dubai - DNS workaround to 8.8.8.8
Thanks for sharing this workaround! DNS issues with cdn.sanity.io in Dubai and the UAE are unfortunately a recurring problem that affects several users in the region. Your solution of switching to Google's public DNS (8.8.8.8) is actually one of the most common and effective workarounds.
Why This Happens
The issue typically stems from local ISP DNS servers in the UAE/Dubai region having problems resolving cdn.sanity.io correctly. This isn't a problem with Sanity's infrastructure itself (which runs on Google's global CDN network), but rather with how some regional DNS providers handle the domain resolution.
Alternative Solutions
Besides switching to Google DNS (8.8.8.8 or 8.8.4.4), you can also try:
- Cloudflare DNS: Use
1.1.1.1or1.0.0.1as your DNS servers - OpenDNS: Try
208.67.222.222or208.67.220.220 - VPN: If DNS changes don't work, a VPN can route around regional network issues
- Router-level DNS: Configure DNS at your router instead of individual devices to fix it for your entire network
For Production Applications
If you're deploying an application that will be accessed by users in Dubai/UAE, keep in mind that they may experience similar issues. You might want to:
- Add a troubleshooting note in your app's help documentation
- Consider implementing error handling that provides helpful messages when assets fail to load
- Test your application from UAE-based networks or VPNs before launch
The good news is that once DNS is properly configured, cdn.sanity.io delivers excellent performance in the region since it leverages Google's global edge network with servers positioned worldwide for optimal delivery.
Show original thread5 replies
Was this answer helpful?
Sanity – Build the way you think, not the way your CMS thinks
Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.
