AKS
AKS copied to clipboard
Azure
dial tcp: lookup misbehaving
Today around noon I have been experiencing this behavior on my cluster
rpc error: code = Unknown desc = Get "https://dev.azure.com/bt-corretora/Procam/_git/BT.Alert.Api.Infra/info/refs?service=git-upload-pack": dial tcp: lookup dev.azure.com on 10.0.0.10:53: server misbehaving\
Hello @dmacobr .
Have you tried to restart the coredns pods from kube-system namespace ?
BR
@justindavies We also see this error on all of our clusters from time to time. After restarting coredns it seems to work again for some time, but the error comes back after some hours. Maybe it's related to the kubernetes upgrade to version 1.24, at least it comes up far more often after that. There must be a solution for this, we cannot restart services manually to be able to deploy to our clusters
Today around noon I have been experiencing this behavior on my cluster
rpc error: code = Unknown desc = Get "https://dev.azure.com/bt-corretora/Procam/_git/BT.Alert.Api.Infra/info/refs?service=git-upload-pack": dial tcp: lookup dev.azure.com on 10.0.0.10:53: server misbehaving\
https://allgoodsfree.com/dial-tcp-lookup-buy-itunes-apple-com/ Need to insist on whether the requested link domain name is correct, the official production environment and the sandbox test
It should be that you use the sandbox account to request the official production link https://allgoodsfree.com/dial-tcp-lookup-buy-itunes-apple-com/ Need to insist on whether the requested link domain name is correct, the official production environment and the sandbox test environment
I have been facing same issue, where once in 5 time dev.azure.com is not resolved and this make it worst for me as i am using GitOps which mean if code is not there terminate all resource (in some case) and thus ruined all the affort to automate. Now looking to migrate away from AzureDevOps because of this.
MS $ucks!
Related issue use in ArgoCD too due to this. https://github.com/argoproj/argo-cd/issues/14956
![microsoft-github-policy-service[bot] avatar](https://avatars.githubusercontent.com/in/95686?v=4 "Published by a pub.dev verified publisher"){kind=small}
Action required from @aritraghosh, @julia-yin, @AllenWen-at-Azure
Hi there :wave: AKS bot here. This issue has been tagged as needing a support request so that the AKS support and engineering teams have a look into this particular cluster/issue.
Follow the steps here to create a support ticket for Azure Kubernetes Service and the cluster discussed in this issue.
Please do mention this issue in the case description so our teams can coordinate to help you.
Thank you!
Hi @dmacobr , are you still seeing this issue? If it is the case, could you please file a support request and share the request ticket number, @SriHarsha001 can help investigate the issue.
This issue will now be closed because it hasn't had any activity for 7 days after stale. dmacobr feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.