question

DanielFrancodosReisAlves-9276 avatar image
0 Votes"
DanielFrancodosReisAlves-9276 asked DanielFrancodosReisAlves-9276 commented

AKS with Azure private DNS zone

Hello,
We set up a AKS with a private DNS zone, so we didn't need to use the external address for AzureSQL and MySQL, keeping all the trafic internal in our vlan. It was working great for the last 105 days (the amount time the AKD is up), till yestarday when sudenly the AKS stopped resolving the DNS zone, and all the hosted pods lost connection with their databases.

We deleted the custom DNS zone and recreated it with all the same records, with no luck.

As a workaround we changed all the pods to "talk" using the MSSQL and MySQL IP address, it worked fine.

We have other resource group with the same construction that is working fine.

Our AKS version is 1.18.14.

Thanks in advance!

azure-kubernetes-service
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Just to check, your using private link for SQL? So you have a privatelink.database.windows.net zone setup?

0 Votes 0 ·

Hello Sam.
Yes, we created a Private DNS Zone named ourcompany.local that we are using within thte private network we have for the entire resource group.

To make it easy to undertand, we have a network interface that we attached on our Azure Database (MySQL and MSSQL), so we have a private IP for those guyz (like 192.168.xxx.xxx) and on top of that we have the DNS service that we create.

So, insted of pointing to the specific IP we create a DNS like mssql.ourcompany.local for the IP 192.168.xxx.xxx and worked like a charm till yestarday when for some reason the AKS cluster can't resolve this DNS anymore. Note that we create a VM on the resource group using Windows Server and neither the VM could resolve the Private DNS Zone.

0 Votes 0 ·

0 Answers