kubernetes

Manage CoreDNS configuration in Kubernetes clusters for DNS forwarding and stub zones.

Updated Mar 6, 2026

Search Tags:#troubleshooting #networking #kubernetes #dns #cluster #coredns

Ready to run

npx skills add https://github.com/renne/skills --skill kubernetes-renne

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kubernetes
Source: https://github.com/renne/skills/tree/main/coredns/kubernetes
Command: npx skills add https://github.com/renne/skills --skill kubernetes-renne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you configure, manage, and troubleshoot CoreDNS, the default DNS server in Kubernetes, ensuring reliable name resolution for your cluster services and pods.

Core Features & Use Cases

CoreDNS Configuration: Understand and modify the Corefile for custom DNS setups, including forwarding, caching, and stub zones.
Kubernetes DNS: Learn how CoreDNS serves records for Services and Pods within the cluster.
Troubleshooting: Diagnose and resolve common DNS issues affecting pod communication and external access.
Use Case: You need to route specific internal domain queries to a corporate DNS server while maintaining default Kubernetes DNS resolution.

Quick Start

Use the kubernetes skill to add a stub zone for 'internal.corp' to the CoreDNS configuration, forwarding queries to '10.10.10.1'.

Frequently Asked Questions about kubernetes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I configure CoreDNS forwarding for custom domains in a Kubernetes cluster?▼

To configure CoreDNS forwarding in a Kubernetes cluster, you modify the Corefile to add a stub zone, forwarding specific domain queries like 'internal.corp' to a custom DNS server while maintaining default cluster DNS resolution.

Why does pod DNS resolution fail in Kubernetes and how can I troubleshoot it?▼

Pod DNS resolution in Kubernetes can fail due to misconfigured CoreDNS plugins like 'kubernetes', 'forward', or 'cache'. You can troubleshoot pod DNS failures by diagnosing CoreDNS configuration and checking cluster DNS setup.

How do I set up split-horizon DNS for internal and external queries in Kubernetes?▼

You set up split-horizon DNS in Kubernetes by customizing the CoreDNS Corefile, routing specific internal domain queries to a corporate DNS server while allowing default resolution for external traffic.

Can I dynamically reload CoreDNS configuration in Kubernetes without restarting pods?▼

Yes, you can dynamically reload CoreDNS configuration in Kubernetes by utilizing the 'reload' plugin within the Corefile, allowing changes to take effect without manually restarting CoreDNS pods.

What is the best way to diagnose cluster DNS issues affecting Kubernetes service communication?▼

The best way to diagnose cluster DNS issues affecting Kubernetes service communication is to inspect CoreDNS configurations and utilize plugins like 'kubernetes' and 'cache' to identify and resolve name resolution failures.

When do I need to customize CoreDNS caching for Kubernetes networking?▼

You need to customize CoreDNS caching for Kubernetes networking when optimizing DNS query response times or managing resolution behavior for specific stub zones within your cluster.