Calico Calico node unable to resolve DNS.

Calico node lacks proper DNS configuration or access to a DNS server.

Understanding Calico

Calico is a powerful open-source networking and network security solution for containers, virtual machines, and native host-based workloads. It is designed to provide a scalable networking fabric across a range of environments, including Kubernetes, OpenShift, and OpenStack. Calico leverages the Linux kernel's native capabilities to deliver high-performance networking and security policies.

Identifying the Symptom

One common issue that users may encounter when using Calico is the inability of a Calico node to resolve DNS. This problem manifests as network connectivity issues, where services or applications running on the node cannot reach external resources or other nodes within the cluster due to DNS resolution failures.

Exploring the Issue: CALICO-1021

The error code CALICO-1021 indicates that a Calico node is unable to resolve DNS queries. This can severely impact the functionality of applications relying on DNS for service discovery and external communication. The root cause often lies in misconfigured DNS settings or lack of access to a DNS server.

Common Causes

  • Incorrect DNS server IP addresses configured on the node.
  • Network policies blocking DNS traffic.
  • DNS server unavailability or misconfiguration.

Steps to Resolve the DNS Issue

To resolve the DNS resolution issue on a Calico node, follow these steps:

Step 1: Verify DNS Configuration

Check the DNS configuration on the affected node. Ensure that the DNS server IP addresses are correctly specified in the /etc/resolv.conf file. You can view the file using:

cat /etc/resolv.conf

Ensure that the DNS server IPs are reachable and correct.

Step 2: Test DNS Connectivity

Use the nslookup or dig command to test DNS resolution from the node:

nslookup google.com

If the command fails, it indicates a DNS resolution problem.

Step 3: Check Network Policies

Ensure that Calico network policies are not blocking DNS traffic. Review the policies using:

calicoctl get networkpolicy -o yaml

Adjust the policies to allow DNS traffic if necessary.

Step 4: Verify DNS Server Availability

Ensure that the DNS server is operational and accessible from the node. You can ping the DNS server to check its availability:

ping <dns-server-ip>

If the server is unreachable, investigate network connectivity issues.

Additional Resources

For more information on configuring DNS in Kubernetes, refer to the official Kubernetes DNS documentation. Additionally, the Calico documentation provides comprehensive guidance on network policy management and troubleshooting.

Master

Calico

in Minutes — Grab the Ultimate Cheatsheet

(Perfect for DevOps & SREs)

Most-used commands
Real-world configs/examples
Handy troubleshooting shortcuts
Your email is safe with us. No spam, ever.

Thankyou for your submission

We have sent the whitepaper on your email!
Oops! Something went wrong while submitting the form.

Calico

Cheatsheet

(Perfect for DevOps & SREs)

Most-used commands
Your email is safe with us. No spam, ever.

Thankyou for your submission

We have sent the whitepaper on your email!
Oops! Something went wrong while submitting the form.

MORE ISSUES

Calico Calico node unable to access specific BGP attribute.
Misconfiguration or inaccessibility of the BGP attribute.
Calico Calico node unable to access specific BGP policy.
BGP policy configuration is incorrect or unreachable.
Calico Calico node unable to access specific VLAN.
VLAN configuration issues or network reachability problems.
Calico Calico node unable to access specific BGP community.
Misconfiguration or network reachability issues with the BGP community.
Calico Calico node unable to access specific BGP route.
Misconfiguration in BGP route settings or network reachability issues.
Calico Calico node unable to access specific BGP peer.
BGP peer configuration is incorrect or the peer is unreachable.
Calico Calico node unable to access specific VRF.
VRF configuration is incorrect or the VRF is not reachable.
Calico Calico node unable to access specific AS number.
AS number configuration is incorrect or unreachable.
Calico Calico node unable to access specific CIDR range.
Incorrect CIDR range configuration or network reachability issues.
Calico Calico node unable to access specific interface.
Interface configuration issues.
Calico Calico node unable to access specific gateway.
Gateway configuration issues or network reachability problems.
Calico Calico node unable to access specific route.
Route configuration may be incorrect or the route may not be reachable.
Calico Calico node unable to access specific subnet.
Subnet configuration issues or network reachability problems.
Calico Calico node unable to access specific IP address.
IP address configuration issue or network reachability problem.
Calico Calico node unable to access specific endpoint.
The endpoint configuration may be incorrect or the endpoint may not be reachable.
Calico Calico node unable to access specific pod.
Pod configuration issues or network policy misconfigurations.
Calico Calico node unable to access specific namespace.
Namespace configuration issues or access restrictions.
Calico Calico node unable to access specific service.
Service configuration issues or network policies blocking access.
Calico Calico node unable to access internal network.
Network policies and routing configurations may be misconfigured, preventing internal access.
Calico Calico node unable to access cloud metadata service.
Network misconfiguration preventing access to the cloud metadata service.
Calico Calico node unable to access etcd.
Network connectivity issues or etcd service not running.
Calico Calico node unable to access external network.
Network policies and routing configurations may be blocking external access.
Calico Calico node experiencing high CPU usage.
High CPU usage can be caused by various factors such as misconfiguration, resource constraints, or excessive network traffic.
Calico Calico node experiencing high memory usage.
High memory usage can be caused by various factors such as misconfiguration, resource-intensive workloads, or memory leaks.
Calico Calico node unable to access Kubernetes API.
Network connectivity issues or misconfiguration preventing access to the Kubernetes API server.
Calico Calico node is experiencing connectivity issues due to time synchronization problems.
The Calico node has incorrect time settings, leading to potential connectivity and synchronization issues.
Calico Calico node unable to join cluster.
Network configuration issues preventing node communication.
Calico Calico BGP peer not reachable.
Network connectivity issues or incorrect BGP configuration.
Calico Calico IP pool incorrectly configured.
The IP pool configuration does not match the desired CIDR range.
Calico Calico node unable to reach API server.
Network connectivity issues or API server is not accessible from the node.
Calico Calico node unable to resolve DNS.
Calico node lacks proper DNS configuration or access to a DNS server.
Calico IP address conflict detected.
Conflicting IP allocations in the network.
Calico Calico metrics not available.
Metrics server not running or misconfigured.
Calico CALICO-1017
Calico version mismatch across nodes.
Calico Network policy not enforced.
Network policy is incorrectly defined or the policy controller is not running.
Calico VXLAN mode not working.
Incorrect VXLAN configuration or unsupported network infrastructure.
Calico Calico node pods stuck in CrashLoopBackOff.
Calico node pods are unable to start due to insufficient resources or configuration errors.
Calico IPAM block not released.
CALICO-1013: IPAM block not released.
Calico Node-to-node mesh not functioning.
BGP configurations are incorrect or node-to-node mesh is not enabled.
Calico Calicoctl command fails with authentication error.
Incorrect credentials or insufficient permissions for accessing the datastore.
Calico Service IPs not reachable.
Check kube-proxy configuration and ensure Calico is correctly handling service IPs.
Calico Calico CNI plugin not found.
The Calico CNI plugin is not installed or configured correctly on the node.
Calico Packet drops observed in the network.
MTU mismatch causing packet drops.
Calico IP-in-IP encapsulation not working.
IP-in-IP configuration is not enabled on all nodes.
Calico IP pool is exhausted.
The IP pool configured in Calico has run out of available IP addresses.
Calico Datastore connection failure.
Incorrect datastore configuration or network issues preventing access.
Calico Felix is not running.
Felix is not running due to misconfiguration or errors in the logs.
Calico Policy not applied to workload.
Policy not applied to workload.
Calico BGP session is not established.
Incorrect BGP configuration or unreachable peer IPs.
Calico Calico node is not ready.
The calico-node pod is not functioning correctly, possibly due to network connectivity issues.

Backed by

Platform

AI OpsAlert Grouping & De-DuplicationPlayBooksKubernetes Bot

Resources

DocumentationFun For DevsBlog

Contact

Contact UsAbout UsCareersTerms and ConditionsPrivacy PolicyShipping & and Delivery PolicyCancellation & Refund Policy

Connect

Slack CommunityGithubLinkedInX (Twitter)
Made with ❤️ in Bangalore & San Francisco 🏢

Doctor Droid