Calls to core DNS are timing out

Jan Jannink 0 Reputation points
2025-06-26T19:42:46.0866667+00:00

We are seeing timeouts of this type in the logs of our kubernetes cluster as we contact core DNS:


requests.exceptions.ConnectionError: HTTPSConnectionPool(host='openaipublic.blob.core.windows.net', port=443): Max retries exceeded with url: /encodings/cl100k_base.tiktoken (Caused by NameResolutionError("
Azure Kubernetes Service
Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,462 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Anusree Nashetty 4,790 Reputation points Microsoft External Staff Moderator
    2025-06-30T21:13:03.75+00:00

    Hi Jan Jannink,

    As per my understanding, I have provided the troubleshooting steps:

    Check if CoreDNS pods are restarting or under pressure. If you're using coredns, it may be misconfigured or not scaling.

    Enable NodeLocal DNS Cache, this significantly reduces DNS lookup latency and load on CoreDNS. https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/

    If using Azure-provided DNS: Ensure egress to Azure DNS IP 168.63.129.16 is not blocked. Confirm CoreDNS is forwarding to this IP.

    If using custom DNS: Verify the upstream DNS server is reachable from the node subnet. Ensure the custom DNS is responsive and not intermittently timing out.

    If you have any further queries, let me know. If the information is helpful, please click on Upvote.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.