Dealing with server misbehaving #AKS #kubernetes #azure

Sergii Bielskyi
Aug 31, 2018 · 1 min read

Recently, I found the issue with connecting to my node #kubernetes like this

“Error from server: error dialing backend: dial tcp: lookup k8s-agentpool on ………:53: server misbehaving”

This was happened due to changing Public IP address from my node as I understood correctly. So, I have started to think what I can do to solve this problem. When I tried to execute command like kubectl get pods or kubectl get nodes I saw the response from cluster without any issues but when I tried to run the command like kubectl logs pod_name I saw the error as I described above.

Simple workaround to sort out this mistake for me was just rebooting node and waiting few minutes when node was started and applied changes.

Sergii Bielskyi

Written by

Cloud is more that you imagine… Cloud Infrastructure Architect | Microsoft Azure MVP | Founder of IoT community in Ukraine | MCPD | MCTS | MCP

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade