Container Service for Kubernetes:DNS troubleshooting

Table of contents

Diagnostics procedure

Terms

• internal domain name: the domain name that is used by CoreDNS to exposes services. An internal domain name ends with .cluster.local. DNS queries for the internal domain name are resolved based on the DNS cache of CoreDNS instead of the upstream DNS servers.

• external domain name: the domain names that are resolved by authoritative DNS provided by third-party DNS service providers, Alibaba Cloud DNS, or Alibaba Cloud DNS PrivateZone. Cluster external domain names are resolved by the upstream DNS servers of CoreDNS. CoreDNS only forwards DNS queries to the upstream DNS servers.

• application pod: the pods other than the pods of system components in a Kubernetes cluster.

• application pod that uses CoreDNS for DNS resolutions: the application pods that use CoreDNS to process DNS queries.

• application pod that uses NodeLocal DNSCache for DNS resolutions: the application pods to which DNSConfig is injected. After you install NodeLocal DNSCache in your cluster, you can configure DNS settings by injecting DNSConfig to application pods. This way, DNS queries of these pods are first sent to NodeLocal DNSCache. If NodeLocal DNSCache fails to process the queries, the queries are sent to the kube-dns Service of CoreDNS.

Troubleshooting procedure

1. Determine the cause of the exception. For more information, see the Common error messages section of this topic.

   • If the error message indicates that the domain name does not exist, refer to Check the domain name in the Troubleshooting section.

   • If the error message indicates that connections to the DNS server cannot be established, refer to Check the frequency of errors in the Troubleshooting section.

2. If the issue persists, perform the following steps:

   • Check whether CoreDNS is specified in the DNS configurations of the application pod. For more information, see the Diagnose the DNS configurations of application pods section of this topic.

     • If CoreDNS is not specified in the DNS configurations, the client may run at full load or the conntrack table may be full. For more information, see the What do I do if DNS resolutions fail because the client is overloaded? or What do I do if the conntrack table is full? section of this topic.

     • If CoreDNS is specified in the DNS configurations, perform the following steps:

       1. Check the status of the CoreDNS pods. For more information, see the Diagnose the status of the CoreDNS pod and What do I do if CoreDNS pods do not run as expected? sections of this topic.

       2. Check the run logs of the CoreDNS pods. For more information, see the Diagnose the run logs of CoreDNS and What do I do if the external domain name of my cluster cannot be resolved? sections of this topic.

       3. Check whether the issue can be stably reproduced.

          1. If the issue can be stably reproduced, refer to the Diagnose the DNS query logs of CoreDNS and Diagnose the network connectivity between application pods and the CoreDNS pod sections of this topic.

          2. If the issue cannot be stably reproduced, refer to the Capture packets section of this topic.

   • If NodeLocal DNSCache is specified in the DNS configuration, refer to the What do I do if NodeLocal DNSCache does not work? and What do I do if domain names that are added to Alibaba Cloud DNS PrivateZone cannot be resolved? sections of this topic.

3. If the issue persists, submit a ticket.

Common error messages

Troubleshooting

Diagnostics methods

Diagnose the DNS configurations of application pods

• Commands

  # Run the following command to query the YAML file of the foo pod. Then, check whether the dnsPolicy field in the YAML file is set to a proper value. 
  kubectl get pod foo -o yaml
  
  # If the dnsPolicy field is set to a proper value, check the DNS configuration file of the pod. 
  
  # Run the following command to log on to the containers of the foo pod by using bash. If bash does not exist, use sh. 
  kubectl exec -it foo bash
  
  # Run the following command to query the DNS configuration file. Then, check the DNS server addresses in the nameserver field. 
  cat /etc/resolv.conf

• DNS policy settings

  The following sample code provides a pod template that is configured with DNS policy settings:

  apiVersion: v1
  kind: Pod
  metadata:
    name: <pod-name>
    namespace: <pod-namespace>
  spec:
    containers:
    - image: <container-image>
      name: <container-name>
  
  # The default value of the dnsPolicy field is ClusterFirst. 
    dnsPolicy: ClusterFirst
  # The following code shows the DNS policy settings that are applied when NodeLocal DNSCache is used. 
    dnsPolicy: None
    dnsConfig:
      nameservers:
      - 169.254.20.10
      - 172.21.0.10
      options:
      - name: ndots
        value: "3"
      - name: timeout
        value: "1"
      - name: attempts
        value: "2"
      searches:
      - default.svc.cluster.local
      - svc.cluster.local
      - cluster.local
  
    securityContext: {}
    serviceAccount: default
    serviceAccountName: default
    terminationGracePeriodSeconds: 30

  Value of dnsPolicy	Description
  Default	You can use this value if internal access from within the cluster is not required. The pod uses DNS servers that are specified in the /etc/resolv.conf file of the Elastic Compute Service (ECS) instance.
  ClusterFirst	This is the default value. The IP address of the kube-dns Service is used as the address of the DNS server that is used by the pod. For pods that use the host network, a value of ClusterFirst has the same effect as the value of Default.
  ClusterFirstWithHostNet	For pods that use the host network, a value of ClusterFirstWithHostNet has the same effect as the value of ClusterFirst.
  None	If you use this value, you can configure self-managed DNS servers and custom parameters in the dnsConfig section. If you enable the automatic injection of dnsConfig for NodeLocal DNSCache, the IP address of the local DNS cache and the IP address of the kube-dns Service are specified as the addresses of the DNS servers.

Diagnose the status of the CoreDNS pod

Diagnose the run logs of CoreDNS

Commands

kubectl -n kube-system logs -f --tail=500 --timestamps coredns-xxxxxxxxx-xxxxx

Diagnose the DNS query logs of CoreDNS

Commands

The DNS query logs of CoreDNS are generated only when the log plug-in of CoreDNS is enabled. For more information about how to enable the log plug-in, see Configure CoreDNS.

Run the command that you use to query the run logs of CoreDNS. For more information, see the Diagnose the run logs of CoreDNS section of this topic.

Diagnose the network connectivity of the CoreDNS pod

Procedure

1. Log on to the node on which the CoreDNS pod runs.

2. Run the ps aux | grep coredns command to query the ID of the CoreDNS process.

3. Run the nsenter -t <pid> -n bash command to enter the network namespace to which CoreDNS belongs. Replace pid with the process ID that you obtained in the previous step.

4. Test the network connectivity.

   1. Run the telnet <apiserver_clusterip> 6443 command to test the connectivity to the Kubernetes API server of the cluster.

      Replace apiserver_clusterip with the IP address of the Service that is used to expose the Kubernetes API server of the cluster.

   2. Run the dig <domain> @<upstream_dns_server_ip> command to test the connectivity between the CoreDNS pod and the upstream DNS servers.

      Replace domain with the test domain name and upstream_dns_server_ip with the IP addresses of the upstream DNS servers, which are 100.100.2.136 and 100.100.2.138 by default.

Troubleshooting

Diagnose the network connectivity between application pods and the CoreDNS pod

Procedure

1. Use one of the following methods to connect to the container network of the application pods.

   • Method 1: Run the kubectl exec command.

   • Method 2:

     1. Log on to the node on which the application pods run.

     2. Run the ps aux | grep <Application process name> command to query the ID of the application process.

     3. Run the nsenter -t <pid> -n bash command to enter the namespace to which the application pods belong.

        Replace pid with the process ID that you obtained in the previous step.

   • Method 3: If the application pods frequently restart, perform the following steps:

     1. Log on to the node on which the application pods run.

     2. Run the docker ps -a | grep <Application container names> command to query the containers whose names start with k8s_POD_ . Record the sandboxed container IDs that are returned.

     3. Run the docker inspect <Sandboxed container ID> | grep netns command to query the path of the network namespace to which the container belongs in the /var/run/docker/netns/xxxx file.

     4. Run the nsenter -n<netns path> -n bash command to enter the network namespace.

        Replace netns path with the path that you obtained in the previous step.

        Note

        Do not add spaces between -n and <netns path>.

2. Test the network connectivity.

   1. Run the dig <domain> @<kube_dns_svc_ip> command to test the connectivity between the application pods and the kube-dns Service.

      Replace <domain> with the test domain name and <kube_dns_svc_ip> with the IP address of the kube-dns Service in the kube-system namespace.

   2. Run the ping <coredns_pod_ip> command to test the connectivity between the application pods and the CoreDNS pod.

      Replace <coredns_pod_ip> with the IP address of the CoreDNS pod in the kube-system namespace.

   3. Run the dig <domain> @<coredns_pod_ip> command to test the connectivity between the application pods and the CoreDNS pod.

      Replace <domain> with the test domain name and <coredns_pod_ip> with the IP address of the CoreDNS pod in the kube-system namespace.

Troubleshooting

Capture packets

If you cannot identify the issue, capture and diagnose packets.

1. Log on to the nodes on which the application pods and CoreDNS pod run.

2. Run the following command on each ECS instance to capture all recent packets received on port 53:

   tcpdump -i any port 53 -C 20 -W 200 -w /tmp/client_dns.pcap

3. Diagnose the packets that are transferred during the time period in which the error occurred.

   Note

   • Packet capture does not affect your service and only causes a slight increase in the CPU utilization and disk I/O.

   • The preceding command rotates the captured packets and can generate up to 200 .pcap files. Each .pcap file is 20 MB in size.

What do I do if the external domain name of my cluster cannot be resolved?

Problem description

The internal domain name of the cluster can be resolved, but the external domain name of the clustercannot be resolved.

Cause

An error in the upstream DNS server when the external domain name is resolved.

Solution

Check the DNS query logs of CoreDNS.

Common DNS query log

# If the response code is NOERROR, the domain name is resolved without errors. 
[INFO] 172.20.2.25:44525 - 36259 "A IN redis-master.default.svc.cluster.local. udp 56 false 512" NOERROR qr,aa,rd 110 0.000116946s

Common response codes

If the DNS query log of CoreDNS displays NXDOMAIN, SERVFAIL, or REFUSED for the external domain name of the cluster, the upstream DNS server of CoreDNs returns an error.

By default, DNS servers 100.100.2.136 and 100.100.2.138 provided by Virtual Private Cloud (VPC) are used as the upstream DNS servers of CoreDNS. To resolve the preceding errors, submit a ticket to the ECS team. You need to include the information that is described in the following table in the ticket.

What do I do if domain names of headless Services cannot be resolved?

Problem description

CoreDNS cannot resolve domain names of headless Services.

Cause

In a CoreDNS version earlier than 1.7.0 is used, CoreDNS may unexpectedly exit if network jitters occur in the Kubernetes API server of the cluster. As a result, the domain names of headless Services are not updated when CoreDNS is down.

Solution

Update CoreDNS to 1.7.0 or later. For more information, see [Component Updates] Update CoreDNS.

What do I do if domain names of headless Services cannot be resolved after I update CoreDNS?

Problem description

Earlier versions of open source components, such as etcd, Nacos, and Kafka, cannot work as expected if Kubernetes 1.20 or later and CoreDNS 1.8.4 or later are used.

Cause

CoreDNS 1.8.4 or later preferably uses the EndpointSlice API to synchronize the IP addresses of the Services in your cluster. Some open source components use the service.alpha.kubernetes.io/tolerate-unready-endpoints annotation provided by the Endpoint API during the initialization phase to publish Services that are not ready. This annotation has been deprecated in the EndpointSlice API and replaced by publishNotReadyAddresses. Therefore, you cannot release Services that are not ready after you update CoreDNS. As a result, the open source components cannot perform service discovery.

Solution

Check whether the YAML file or Helm Chart file of the open source component contains the service.alpha.kubernetes.io/tolerate-unready-endpoints annotation. If the open source component contains the annotation, the open source component may fail to work as expected. In this case, you need to upgrade the open source component or consult the open source component community.

What do I do if domain names of StatefulSet pods cannot be resolved?

Problem description

The domain names of StatefulSet pods cannot be resolved.

Cause

If a StatefulSet is exposed by using a headless Service, the ServiceName parameter in the pod YAML template must be set to the name of the headless Service. Otherwise, you cannot access the domain names of the StatefulSet pods, such as pod.headless-svc.ns.svc.cluster.local. However, you can access the domain name of the headless Service, such as headless-svc.ns.svc.cluster.local.

Solution

Set the ServiceName parameter in the pod YAML template to the name of the headless Service that is used to expose the StatefulSet pods.

What do I do if DNS queries are blocked by security group rules or the network ACLs that are associated with vSwitches?

Problem description

DNS resolution failures of CoreDNS persist on some or all nodes.

Cause

The security group rules or network access control lists (ACLs) that control the network communication of the ECS instance block UDP port 53.

Solution

Modify the security group rules or network ACLs to open UDP port 53.

What do I do if container network connectivity errors occur?

Problem description

DNS resolution failures of CoreDNS persist on some or all nodes.

Cause

UDP port 53 is blocked due to container network connectivity errors or other causes.

Solution

submit a ticket.

What do I do if CoreDNS pods are overloaded?

Problem description

• The DNS resolution latency of CoreDNS is high, or DNS resolution failures of CoreDNS persist or occasionally occur on some or all nodes.

• Check the status of CoreDNS pods and check whether the CPU and memory usage is about to reach the upper limit.

Cause

The number of replicated pods that are configured for CoreDNS is insufficient to handle DNS queries.

Solution

• Use NodeLocal DNSCache to improve DNS resolution efficiency and reduce the load on CoreDNS. For more information, see Configure NodeLocal DNSCache.

• Scale out CoreDNS pods to ensure that the peak CPU utilization of each pod is less than the amount of idle CPU resources of the node.

What do I do if the DNS query load is not balanced among CoreDNS pods?

Problem description

• The DNS resolution latency of CoreDNS is high, or DNS resolution failures of CoreDNS persist or occasionally occur on some nodes.

• The status of CoreDNS pods shows that the CPU utilization is different among the pods.

• The number of replicated pods that are configured for CoreDNS is less than two or multiple CoreDNS pods are deployed on the same node.

Cause

DNS queries are not evenly distributed among CoreDNS pods due to imbalanced pod scheduling or improper SessionAffinity settings of the kube-dns Service.

Solution

• Scale out CoreDNS pods and schedule the pods to different nodes.

• You can delete the SessionAffinity parameter from the configuration of the kube-dns Service. For more information, see the Configure kube-dns Service of the "Configure ACK to automatically update CoreDNS" topic.

What do I do if CoreDNS pods do not run as expected?

Problem description

• The DNS resolution latency of CoreDNS is high, or DNS resolution failures of CoreDNS persist or occasionally occur on some nodes.

• CoreDNS pods are not in the Running state or the number of pod restarts continuously increases.

• The CoreDNS log data indicates that errors occurred.

Cause

CoreDNS pods do not run as expected due to improper settings in the YAML file or the CoreDNS ConfigMap.

Solution

Check the status and run logs of CoreDNS pods.

Common error logs and solutions

What do I do if DNS resolutions fail because the client is overloaded?

Problem description

DNS resolution errors occur occasionally or during peak hours. The monitoring information about the ECS instance indicates an abnormal retransmission rate of the network interface controller (NIC) and an abnormal CPU utilization.

Cause

The ECS instance that hosts the pod that sends the DNS query to CoreDNS is fully loaded, which causes UDP packet loss.

Solution

• We recommend that you submit a ticket to troubleshoot the issue.

• Use NodeLocal DNSCache to improve DNS resolution efficiency and reduce the load on CoreDNS. For more information, see Configure NodeLocal DNSCache.

What do I do if the conntrack table is full?

Problem description

• CoreDNS frequently fails to resolve domain names on some or all nodes during peak hours, but can resolve domain names as expected during off-peak hours.

• Run the dmesg -H command on the instance and check the log that is generated during the period in which the resolution fails. The log contains the keyword conntrack full.

Cause

The conntrack table of the Linux kernel is full. As a result, requests that are sent over UDP or TCP cannot be processed.

Solution

Increase the maximum number of entries in the conntrack table of the Linux kernel. For more information, see the How do I increase the maximum number of tracked connections in the conntrack table of the Linux kernel? section of the "FAQ about container networks" topic.

What do I do if the autopath plug-in does not work as expected?

Problem description

• The external domain name occasionally fails to be resolved or is occasionally resolved to a wrong IP address. However, the internal domain name is resolved as expected.

• When the cluster creates containers at a high frequency, the internal domain name is resolved to a wrong IP address.

Cause

The autopath plug-in does not work as expected due to the defects of CoreDNS.

Solution

What do I do if DNS resolutions fail due to concurrent queries for A records and AAAA records?

Problem description

• DNS resolutions of CoreDNS occasionally fail.

• The captured packets or the log of DNS queries to CoreDNS shows that queries for A records and AAAA records are initiated at the same time over the same port.

Cause

• Concurrent DNS queries for A records and AAAA records cause errors of the conntrack table of the Linux kernel, which results in UDP packet loss.

• GNU C Library (libc) whose version is earlier than 2.33 initiates queries for A records and AAAA records at the same time on ARM machines. As a result, the queries time out and are reinitiated. For more information, see GLIBC#26600.

Solution

• Use NodeLocal DNSCache to improve DNS resolution efficiency and reduce the load on CoreDNS. For more information, see Configure NodeLocal DNSCache.

• For images that use libc, such as CentOS or Ubuntu images, update the version of libc to 2.33 or later to prevent the issue that queries for A records and AAAA records are initiated at the same time.

• You can optimize CentOS and Ubuntu images by setting the parameters such as options timeout:2 attempts:3 rotate single-request-reopen.

• If the image that you use is based on Alpine Linux, we recommend that you replace the image with an image that is based on another operating system. For more information, see Alpine.

• A variety of resolution errors may occur when applications written in PHP send DNS queries by using short-lived connections. If you use PHP cURL, you must add CURL_IPRESOLVE_V4 to specify that domain names can be resolved only to IPv4 addresses. For more information, see cURL_setopt.

What do I do if DNS resolutions fail due to IPVS errors?

Problem description

DNS resolutions occasionally fail when nodes are added to or removed from the cluster, nodes are shut down, or CoreDNS is scaled in. In most cases, this situation lasts for about 5 minutes.

Cause

The load balancing mode of kube-proxy is set to IP Virtual Server (IPVS) in your cluster. If you remove IPVS UDP backend pods from nodes that run CentOS or Alibaba Cloud Linux 2 whose kernel versions are earlier than 4.19.91-25.1.al7.x86_64, source port conflicts occur when UDP packets are sent. As a result, the UDP packets are dropped.

Solution

• Use NodeLocal DNSCache to reduce packet loss in IPVS mode. For more information, see Configure NodeLocal DNSCache.

• Shorten the timeout period of UDP sessions in IPVS mode. For more information, see the Change the UDP timeout period in IPVS mode section of the "Configure ACK to automatically update CoreDNS" topic.

What do I do if NodeLocal DNSCache does not work?

Problem description

All DNS queries are sent to CoreDNS instead of NodeLocal DNSCache.

Cause

• DNSConfig is not injected into the application pods. The IP address of the kube-dns Service is configured as the address of the DNS server for the application pods.

• The application pods are deployed by using an image based on Alpine Linux. As a result, DNS queries are concurrently sent to all nameservers, including the local DNS cache and CoreDNS pods.

Solution

• Configure automatic injection for DNSConfig. For more information, see Configure NodeLocal DNSCache.

• If the image that you use is based on Alpine Linux, we recommend that you replace the image with an image that is based on another operating system. For more information, see Alpine.

What do I do if domain names that are added to Alibaba Cloud DNS PrivateZone cannot be resolved?

Problem description

When NodeLocal DNSCache is used, domain names that are added to Alibaba Cloud DNS PrivateZone cannot be resolved, the endpoints of Alibaba Cloud service APIs that contain vpc-proxy cannot be resolved, or domain names are resolved to wrong IP addresses.

Cause

Alibaba Cloud DNS PrivateZone does not support TCP. You must use UDP.

Solution

Add the prefer_udp configuration to CoreDNS. For more information, see Configure CoreDNS.