Azure Private DNS Resolver

Поділитися
Вставка
  • Опубліковано 19 гру 2024

КОМЕНТАРІ • 17

  • @liudmylasoderstrom6226
    @liudmylasoderstrom6226 Рік тому +1

    Great explanation! I wasn’t sure which IP address entered on premise from Azure. But now it’s clear 😊

  • @say2merohit
    @say2merohit Рік тому +1

    OUTSTANDING !! Seamless video edits :)

  • @arpanchakraborty9874
    @arpanchakraborty9874 7 місяців тому +1

    Thanks for this video. Very helpful ❤

  • @arpanchakraborty9874
    @arpanchakraborty9874 7 місяців тому +1

    Excellent video. Thank you

  • @ketanvalsangkar
    @ketanvalsangkar Рік тому +1

    Very good explanation

  • @anthonydelagarde3990
    @anthonydelagarde3990 3 місяці тому

    Great video and explanation

  • @metalmasterlp
    @metalmasterlp Рік тому +1

    Nice explanation thanks

  • @zack.123.
    @zack.123. Рік тому

    Great video thank you. How does this fit in if you have Azure Firewall with DNS proxy?

    • @PatriksTechLightning
      @PatriksTechLightning  Рік тому +1

      Good question !
      The only option you would have on an Azure Firewall is to configure it with the ip address of the "Inbound Endpoint".
      The only thing which is uncertain is resolving on premise DNS names. I've not been able to find any Microsoft articles highlighting this with the Azure Firewall.
      I don't see an issue with other DNS lookup such as private endpoints. I haven't fully tested this scenario yet but it's on my radar.

  • @ketanvalsangkar
    @ketanvalsangkar Рік тому

    Can we sync multiple azure dns private resolver each other is this possible?

  • @noname-mj1qr
    @noname-mj1qr Рік тому

    Great video thanks. I don't understand why they need an entire subnet for outbound endpoints and another one for inbound. If you were building this yourself, you would only need a single address. Seems like that particular bit is very badly designed. (Unless there's a reason for doing it this way that i'm missing?)