external-dns-troubleshooting

Diagnose ExternalDNS synchronization failures in Kubernetes clusters by inspecting logs, RBAC, and provider credentials.

18|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/foxj77/claude-code-skills --skill external-dns-troubleshooting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external-dns-troubleshooting
Source: https://github.com/foxj77/claude-code-skills/tree/main/external-dns-troubleshooting
Command: npx skills add https://github.com/foxj77/claude-code-skills --skill external-dns-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ExternalDNS troubleshooting helps teams quickly identify and fix why DNS records are not created or updated for Kubernetes Services and Ingresses, preventing outages and misrouting.

Core Features & Use Cases

  • Diagnose missing or stale DNS records and provider errors across AWS Route53, Azure DNS, Cloudflare, Google Cloud DNS, and other providers.
  • Inspect the ExternalDNS controller health, RBAC permissions, domain filters, and hostname annotations to discover misconfigurations.
  • Provide guided remediation steps to restore DNS synchronization in both standalone and Flux-managed deployments.

Quick Start

Run a focused troubleshooting session by inspecting ExternalDNS pods and logs to identify the first reported error, then validate provider credentials, domain filters, and annotations.

Frequently Asked Questions about external-dns-troubleshooting

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

FAQPage Schema
Why are my Kubernetes DNS records not updating or showing up in ExternalDNS?

Missing or stale DNS records in ExternalDNS usually stem from provider authentication errors, incorrect domain filters, missing hostname annotations, or insufficient RBAC permissions. Inspecting controller logs reveals the first reported error to diagnose the exact configuration failure.

How do I troubleshoot ExternalDNS provider authentication failures in Kubernetes?

To troubleshoot ExternalDNS provider authentication failures, inspect the controller logs for credential rejection errors and validate provider authentication settings for AWS Route53, Azure DNS, Cloudflare, or Google Cloud DNS to restore DNS synchronization.

What is the best way to diagnose stale DNS records caused by ExternalDNS misconfigurations?

The best way to diagnose stale DNS records is to inspect ExternalDNS pod health, verify domain filters, check hostname annotations, and review RBAC permissions. Guided remediation steps then restore DNS synchronization across providers.

Can I use ExternalDNS troubleshooting for Flux-managed Kubernetes deployments?

Yes, ExternalDNS troubleshooting provides guided remediation steps to restore DNS synchronization in both standalone and Flux-managed Kubernetes deployments by diagnosing provider credentials, zone, and annotation errors.

Do I need specific RBAC permissions to run ExternalDNS troubleshooting?

Yes, you need access to Kubernetes resources and ExternalDNS logs to identify and fix configuration, RBAC, and provider credential issues. Insufficient RBAC permissions prevent the controller from creating or updating DNS records.

What causes ExternalDNS logs to show zone and annotation errors?

Zone and annotation errors in ExternalDNS logs are caused by incorrect domain filters, missing hostname annotations on Services or Ingresses, or provider credential misconfigurations. Inspecting controller health and validating annotations resolves these synchronization failures.