Index of every page on this site: llms.txt
All skills
Run it yourself

This skill should be used when the user asks about "DNS", "domain resolution", "GeoDNS / geo routing", "latency-based routing", "weighted / failover routing", "Route 53 / Cloud DNS", an "A/CNAME/ALIAS record", "anycast", or "DNS TTL / propagation". It gives the global front door that maps a name to the right IP and steers users to the right region or endpoint. Use it whenever a design must direct traffic across regions/data centers, do health-checked failover at the name layer, or expose a stable hostname even if the user doesn't say "DNS".

Use this Skill: https://skilld.dev/gh/proyecto26/system-design-skills/dns

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesprovidersaws.md

≈512 tokens on demand. Your agent reads this file only when SKILL.md points to it.

DNS — AWS

Service mapping

  • Route 53 — managed authoritative DNS on a global anycast network; the default. Hosted zones (public/private), health checks, and routing policies cover every generic option:
    • Simple / Weighted / Latency / Geolocation / Geoproximity / Failover / Multivalue-answer routing policies map 1:1 to the generic policies (geoproximity adds a bias knob to shift traffic between regions).
    • Alias records — Route 53's apex-alias (the generic ALIAS); point the zone apex at an ELB/CloudFront/S3/API Gateway target with no charge for alias queries.
    • Health checks — endpoint, calculated (combine checks), or CloudWatch-alarm based; gate any policy so unhealthy targets drop out.
  • Route 53 Resolver — for hybrid/VPC DNS (inbound/outbound endpoints); not traffic steering.
  • Global Accelerator — anycast IP + health-based failover that reacts faster than DNS (no TTL wait) by steering at the network layer; reach for it when DNS TTL-bound failover is too slow.

When to pick which

Route 53 alias at the apex onto an ELB/CloudFront is the standard front door. Latency routing for speed, geolocation for residency, failover for active-passive DR, weighted for canary. Use Global Accelerator instead when you need sub-TTL failover or a fixed entry IP.

Limits / things that bite (verify against current docs)

  • Health-check failover is still TTL + propagation bound — Global Accelerator exists precisely to beat that.
  • Latency records route by the resolver's AWS-measured latency, not the user's.
  • Alias targets are limited to specific AWS resource types.
  • Per-hosted-zone record counts and health-check counts have soft quotas.

Pitfalls

  • Putting a CNAME at the apex instead of an alias record.
  • Expecting Route 53 failover to be instant (it is not — consider Global Accelerator).
  • Geoproximity bias misconfigured, silently overloading one region.
  • Single hosted zone with no secondary-provider plan for a critical property.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    The skill provides architectural guidance and documentation for DNS configuration across various cloud providers. No security issues were detected.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 228d57d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago

README badge

README badge for proyecto26/system-design-skills/dns