#Need some assistance with azure private endpoints
1 messages · Page 1 of 1 (latest)
@graceful rampart I'm pretty sure they are from what I remember, but I left the office and I'll check tomorrow morning.
no worries, you should have a Private DNS Zone named privatelink.database.windows.net
That dns zone will need to be vnet linked in order for things in the vnet to resolve it.
gotcha, thank you I'll test it tomorrow morning and let you know!
was able to check now
that all seems okay to me. and nslookup isn't resolving?
yeah its not resolving 😦
i mightve went wrong somewhere but i did the steps multiple times
you can see the A record in the zone?
or is the VM configured with a custom DNS server?
vm is using whatever microsoft assigned us
just to be sure
the link name has to have a bunch of random numbers and letters right
do you mean the generated nic?
yeah, the generated nic
yeah that's fine
Go to your vnet, click on DNS... You'll either have "Azure provided" selected or IPs for custom DNS
yeah that's the only other thing I can think of. Might not be using Azure DNS
if you end up checking via the VM, The azure provided dns server should be 168.63.129.16
yeah that's your problem
sorry im not that good with networking lol
that custom DNS server needs to be aware of those private dns zones
just started here 2 days ago and no documentation
ah okok
so to make sure im on the right page
so do I just
- Record set and add those?
those DNS servers are another VM in a domain or something?
i think our director made them and left
lmao
Fingers crossed that he didn't leave 3 envelopes behind...
probably worth investigating whats at those IP addresses and what they're doing as they might be supporting DNS for other things.
if you need to leave them as is, looks like DNS Private Resolver is the preferred solution to link up with the private dns zones.
you could also just create the needed A records on those custom dns servers but that's not good long term
theyre not filling anything
Private Resolver would be in lieu of custom DNS servers.
you would use the private resolver to get the resolution from custom to azure private dns
whilst keeping the custom dns in the chain, assuming it's needed
if they're not actually doing anything then just switch the VM to use azure provided DNS and you should be good to go
You're just adding a redundant forwarder to the chain in that case. From custom DNS, all you need to do is add a conditional forwarder to Azure's recursive resolver.
But, yeah, this. If the VMs aren't actually server up DNS, there's not much reason to point VMs there for DNS lookups.
yeah would work. but who knows where those DNS servers are pointing lmao. I've seen some orgs setup windows DNS in Azure then immediately point it to onprem ignoring everything azure provided.
let me get back to this tomorrow, i have to do more investigation before i say for sure
more stuff in the office lol, infosec gonna wonder why im on my personal laptop lol
Yeah, that's a fair point. Triggering some DNS PTSD now...
Had a client recently that pointed all vnet DNS to a box that just chucked everything back on-prem. Then they created forward zones with naked A records for every private endpoint.
It was horrible...
Only if those custom dns are running in Azure
Yep. Which, from the screenshot above, they are.
Thanks for the help yall, I'll swing back to this post tmrw morning!