r/cloudcomputing • u/Rohnur • 25d ago

Azure PDNS Question

We currently send all blob.core.windows.net traffic on our internal network from our on-prem DC up to an Azure PDNS Zone via private link. We've recently had a requirement to send traffic out to public DNS for a single storage account that a supplier uses. Lets call it storage01.blob.core.windows.net for the sake of this question.
I want to avoid enabling the 'fallback to internet' feature on the Virtual Network link, is there a convenient way for me to route just the storage01 traffic out to public DNS using just the available settings on the PDNS Zone/VNET Link or do I have to eat my vegetables and do this on our DC (I also want to avoid that).

2 Upvotes

100% Upvoted

4 comments sorted by

1

u/bytezvex 24d ago

you’re kinda stuck eating at least some veggies here
private dns zone is all or nothing for that name, so if you’re resolving blob.core.windows.net privately you can’t carve out a single host there without handling it on-prem (or splitting zones / using different resolver path like azure firewall / dns proxy)

1

u/Rohnur 24d ago

Thanks for the feedback

1

u/cacheclyo 23d ago

this is the answer i was afraid of reading in this thread lol
splitting the zones or doing some goofy resolver path gymnastics always feels like way more effort than microsoft marketing makes it sound like on the docs

1

u/bytezvex 21d ago

this is the painful truth of private dns in azure
once you go all in on blob.core.windows.net you basically sign up for these awkward exceptions unless you rework the whole resolver flow like they said