1

I know with external load balancers in azure we can assign a DNS, but can the same be achieved with an internal load balancer? Using MS Private DNS?

abatishchev
  • 98,240
  • 88
  • 296
  • 433
watdo
  • 667
  • 8
  • 22

1 Answers1

0

Based on my knowledge, it's not possible.

Azure private DNS only works for Azure VM.

You could give your feedback to this link, all of the feedback you share in this link will be monitored and reviewed by the Microsoft engineering teams.

Jason Ye
  • 13,710
  • 2
  • 16
  • 25
  • Hi Jason, thanks for the answer - so in the case of Azure Container Services, where internal services can be exposed via an internal load balancer, it must be expected that services consuming containers via the load balancer are expected to request it by IP Address rather than with a DNS??? – watdo Mar 30 '18 at 13:40
  • @watdo That is not same as Azure private DNS, there is a service running in ACS works like DNS, not Azure private DNS. – Jason Ye Mar 30 '18 at 13:47
  • Yep - for components internal to the cluster running off kube-dns is perfectly fine and works well, but exposing services inside the microservices cluster to azure app services within an app service environment privately? I haven't seen a way of using kube-dns for that yet, so assumed we could expose these via an ILB annotated service - and again this seems to work, but means you have to communicate via IP which seems limiting if it ever changes. Am I missing something here? – watdo Mar 30 '18 at 15:17
  • @watdo Sorry for the delay, you are right, we can't use private in this way, maybe we can use IP address, just keep that service running, and do not delete that service, that IP address will not change, even re-create pods. – Jason Ye Apr 02 '18 at 02:26