I've run into a bit of a snag with accessing multiple storage accounts from a virtual network (VNet). We started with a few storage accounts that were accessible by whitelisting their IPs in the VNet. Then, we created a private endpoint for a new storage account, but now I'm facing issues. Since the traffic for all storage accounts is going through the new private DNS zone, the initial storage accounts' IP addresses aren't resolving anymore. Is there a way to handle this situation without having to set up private endpoints for each of the initial storage accounts?
2 Answers
You might want to check the configuration of your private DNS zone. Enabling the internet fallback feature is a standard approach. It ensures that any storage accounts not linked through a private endpoint will still resolve correctly to their public IPs, avoiding the resolution problems you’re facing.
To resolve the issue without enabling private endpoints for all your storage accounts, consider enabling the internet fallback feature for your private DNS zone. This allows storage accounts without private endpoints to resolve to their public IPs instead of leading to an NXDOMAIN error. It's a useful workaround that lets you keep your existing setup without adding more private endpoints.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically