Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Dns Management

  • 429 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

dns-management is a DevOps agent skill that configures Route53, Azure DNS, or CloudFlare records for failover, geo-routing, health checks, and CDN routing when developers point product URLs live.

About

dns-management is an aj-geddes/useful-ai-prompts skill from a library of 259 specialized skills that guides agents through production DNS strategies across AWS Route53, Azure DNS, and CloudFlare. It covers domain and subdomain routing, TTL tuning, weighted canary routing, geographic load balancing, multi-region failover, CDN integration, health-check routing, and zero-downtime migrations. Reference guides include AWS Route53 configuration, DNS failover scripts, CloudFlare DNS setup, and DNS monitoring validation under the skill references directory. Install with `npx skills add aj-geddes/useful-ai-prompts --skill dns-management` for Claude Code, Cursor, or compatible agents. Developers reach for dns-management when launching a product URL, migrating regions, or standing up disaster-recovery failover—not during everyday application coding or local hostname tweaks. Best practices emphasize health checks with failover, documented change control, and avoiding risky DNS edits during active production incidents or outages.

  • A/AAAA/CNAME record planning
  • Subdomain and apex domain setup
  • TTL and propagation troubleshooting
  • CDN and hosting DNS integration
  • Email SPF/DKIM record guidance

Dns Management by the numbers

  • 429 all-time installs (skills.sh)
  • Ranked #381 of 1,039 Cloud & Infrastructure skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill dns-management

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs429
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you configure DNS for production failover?

Configure DNS records, domains, subdomains, TTL, and routing when pointing a product URL to hosting, CDN, or email providers during go-live.

Who is it for?

DevOps and backend engineers launching or migrating production domains who need multi-provider DNS failover and geo-routing reference implementations.

Skip if: Local development hostname tweaks only, or teams with no control over external DNS providers.

When should I use this skill?

User configures DNS records, domain routing, TTL, CDN pointing, geo-routing, failover, or zero-downtime migration during go-live.

What you get

DNS record plan, provider-specific configuration snippets, failover scripts, and health-check routing setup for the target domain.

  • DNS record configuration plan
  • Failover and health-check scripts
  • Provider-specific routing snippets

By the numbers

  • Includes four DNS reference guides under the skill references directory
  • Part of aj-geddes/useful-ai-prompts library containing 259 specialized skills

Files

SKILL.mdMarkdownGitHub ↗

DNS Management

Table of Contents

Overview

Implement DNS management strategies for traffic routing, failover, geo-routing, and high availability using Route53, Azure DNS, or CloudFlare.

When to Use

  • Domain management and routing
  • Failover and disaster recovery
  • Geographic load balancing
  • Multi-region deployments
  • DNS-based traffic management
  • CDN integration
  • Health check routing
  • Zero-downtime migrations

Quick Start

Minimal working example:

# route53-setup.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: route53-config
  namespace: operations
data:
  setup-dns.sh: |
    #!/bin/bash
    set -euo pipefail

    DOMAIN="myapp.com"
    HOSTED_ZONE_ID="Z1234567890ABC"
    PRIMARY_ENDPOINT="myapp-primary.example.com"
    SECONDARY_ENDPOINT="myapp-secondary.example.com"

    echo "Setting up Route53 DNS for $DOMAIN"

    # Create health check for primary
    PRIMARY_HEALTH=$(aws route53 create-health-check \
      --health-check-config '{
        "Type": "HTTPS",
        "ResourcePath": "/health",
        "FullyQualifiedDomainName": "'${PRIMARY_ENDPOINT}'",
        "Port": 443,
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
AWS Route53 ConfigurationAWS Route53 Configuration
DNS Failover ScriptDNS Failover Script
CloudFlare DNS ConfigurationCloudFlare DNS Configuration
DNS Monitoring and ValidationDNS Monitoring and Validation

Best Practices

✅ DO

  • Use health checks with failover
  • Set appropriate TTL values
  • Implement geolocation routing
  • Use weighted routing for canary
  • Monitor DNS resolution
  • Document DNS changes
  • Test failover procedures
  • Use DNS DNSSEC

❌ DON'T

  • Use TTL of 0
  • Point to single endpoint
  • Forget health checks
  • Mix DNS and application failover
  • Change DNS during incidents
  • Ignore DNS propagation time
  • Use generic names
  • Skip DNS monitoring

Related skills

How it compares

Use dns-management for provider record sets and failover; use application load balancers when routing logic belongs inside the app tier instead of DNS.

FAQ

Which DNS providers does dns-management cover?

dns-management documents patterns for AWS Route53, Azure DNS, and CloudFlare. Reference guides include Route53 configuration, CloudFlare setup, failover scripts, and monitoring validation so agents can implement provider-specific routing and health checks.

When should dns-management be used?

dns-management fits production go-live, multi-region failover, geographic load balancing, CDN integration, health-check routing, and zero-downtime domain migrations. It is aimed at traffic management rather than application-level HTTP routing code.

How do you install dns-management?

Install dns-management with `npx skills add aj-geddes/useful-ai-prompts --skill dns-management`. The skill ships inside a 259-skill library using Progressive Disclosure with SKILL.md hub docs and references for deep dives.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.