#Need some assistance with azure private endpoints

1 messages · Page 1 of 1 (latest)

graceful rampart
#

are the private dns zones the private endpoints are using linked to your vnet(s)?

frosty compass
#

@graceful rampart I'm pretty sure they are from what I remember, but I left the office and I'll check tomorrow morning.

graceful rampart
#

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.

frosty compass
#

gotcha, thank you I'll test it tomorrow morning and let you know!

#

was able to check now

graceful rampart
frosty compass
graceful rampart
#

that all seems okay to me. and nslookup isn't resolving?

frosty compass
#

yeah its not resolving 😦

#

i mightve went wrong somewhere but i did the steps multiple times

graceful rampart
#

you can see the A record in the zone?

#

or is the VM configured with a custom DNS server?

frosty compass
#

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

graceful rampart
frosty compass
#

yeah, the generated nic

graceful rampart
#

yeah that's fine

frosty compass
#

and the record is in the zone as well

nimble flicker
#

Go to your vnet, click on DNS... You'll either have "Azure provided" selected or IPs for custom DNS

graceful rampart
#

yeah that's the only other thing I can think of. Might not be using Azure DNS

frosty compass
#

checking now

graceful rampart
#

if you end up checking via the VM, The azure provided dns server should be 168.63.129.16

frosty compass
#

oh looks like its custom

graceful rampart
#

yeah that's your problem

frosty compass
#

sorry im not that good with networking lol

graceful rampart
#

that custom DNS server needs to be aware of those private dns zones

frosty compass
#

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?
graceful rampart
#

those DNS servers are another VM in a domain or something?

frosty compass
#

i think our director made them and left

graceful rampart
#

lmao

nimble flicker
#

Fingers crossed that he didn't leave 3 envelopes behind...

graceful rampart
#

probably worth investigating whats at those IP addresses and what they're doing as they might be supporting DNS for other things.

#

you could also just create the needed A records on those custom dns servers but that's not good long term

frosty compass
#

theyre not filling anything

nimble flicker
#

Private Resolver would be in lieu of custom DNS servers.

frosty compass
#

u guys think it should be best to start from scratch

#

for this particular

graceful rampart
#

whilst keeping the custom dns in the chain, assuming it's needed

graceful rampart
nimble flicker
#

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.

nimble flicker
graceful rampart
#

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.

frosty compass
#

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

nimble flicker
#

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...

hot jetty
nimble flicker
#

Yep. Which, from the screenshot above, they are.

frosty compass
#

Thanks for the help yall, I'll swing back to this post tmrw morning!