For people having this is issue on AKS clusters with custom DNS...
We have done this on all affected nodepools:
$ VMSS=XXX-vmss $ nodeResourceGroup=XXX-worker $ az vmss list-instances -g $nodeResourceGroup -n $VMSS --query "[].id" --output tsv | az vmss run-command invoke --scripts "systemd-resolve --set-dns=your_dns --set-dns=your_dns --set-domain=reddog.microsoft.com --interface=eth0" --command-id RunShellScript --ids @-
For people having this is issue on AKS clusters with custom DNS...
We have done this on all affected nodepools:
$ VMSS=XXX-vmss up=XXX- worker reddog. microsoft. com --interface=eth0" --command-id RunShellScript --ids @-
$ nodeResourceGro
$ az vmss list-instances -g $nodeResourceGroup -n $VMSS --query "[].id" --output tsv | az vmss run-command invoke --scripts "systemd-resolve --set-dns=your_dns --set-dns=your_dns --set-domain=