managing-dns

Configure DNS records, TTL strategies, and DNS-as-code automation across cloud providers.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/masermediagroup-stack/maser-media --skill managing-dns-masermediagroup-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: managing-dns
Source: https://github.com/masermediagroup-stack/maser-media/tree/main/.cursor/skills/community/ai-design-components/skills/managing-dns
Command: npx skills add https://github.com/masermediagroup-stack/maser-media --skill managing-dns-masermediagroup-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Managing DNS records manually across providers leads to propagation delays, misconfigurations, and downtime during migrations or failovers. This Skill provides structured guidance for record selection, TTL planning, DNS-as-code automation, and troubleshooting. ## Core Features & Use Cases - Record Type & TTL Guidance: Decision trees for A, AAAA, CNAME, MX, TXT, SRV, and CAA records, plus TTL strategies for planned changes and failover scenarios. - DNS-as-Code Automation: Patterns for external-dns (Kubernetes), OctoDNS, DNSControl, and Terraform to version-control and sync DNS across Route53, Cloud DNS, Azure DNS, and Cloudflare. - Load Balancing & Failover: GeoDNS, weighted routing, and health-check-based failover configurations for multi-region deployments. - Use Case: When migrating a domain to a new provider, lower the TTL 48 hours ahead, export existing records with OctoDNS, sync to the new provider, and verify propagation across public resolvers with the included scripts. ## Quick Start Ask the assistant to set up automated DNS management for your domain on Kubernetes using external-dns with Route53.

Frequently Asked Questions about managing-dns

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

FAQPage Schema
How do I automate DNS records from Kubernetes?▼

Deploy external-dns in your cluster and annotate Services or Ingresses with external-dns.alpha.kubernetes.io/hostname. The controller watches resources and automatically creates, updates, and deletes records in providers like Route53, Cloud DNS, or Cloudflare.

OctoDNS vs DNSControl for multi-provider DNS management?▼

OctoDNS uses YAML configuration and suits teams preferring declarative files, while DNSControl uses a JavaScript DSL supporting variables, functions, and loops for complex logic. Both offer preview modes and sync one zone definition to multiple providers.

Why can't I create a CNAME record at the zone apex?▼

CNAME records cannot coexist with the SOA and NS records required at the zone apex per RFC 1912. Use an ALIAS record on Route53, CNAME flattening on Cloudflare, or a plain A record pointing to the target IP instead.

How long does DNS propagation take after a change?▼

Maximum propagation time equals the old TTL plus the new TTL plus query time. Lower the TTL to 300 seconds about 48 hours before planned changes, then verify propagation across resolvers like 8.8.8.8 and 1.1.1.1.

Why is external-dns not creating DNS records?▼

Common causes include annotation typos, a domain-filter that excludes your domain, missing provider credentials, or a LoadBalancer still pending an external IP. Check external-dns logs and verify the annotation spelling and policy setting.

Which DNS provider should I choose for multi-cloud infrastructure?▼

Cloudflare suits multi-cloud setups with fast global resolution, built-in DDoS protection, and a free tier. Alternatively, use OctoDNS or DNSControl to synchronize records across Route53, Cloud DNS, and other providers from one configuration.