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.

referencesprovidersazure.md

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

DNS — Azure

Service mapping

Azure splits "host the zone" from "steer the traffic" across two services — know which one a routing policy lives in.

  • Azure DNS — managed authoritative hosting on anycast. Public and private zones, A/AAAA/CNAME/MX/TXT, and alias records (the generic ALIAS, including apex) pointing at Azure resources (Public IP, Front Door, Traffic Manager). This is record hosting — it does not do latency/geo/failover steering.
  • Traffic Manager — DNS-based global traffic routing. This is where the routing policies live: Priority (= failover), Weighted, Performance (= latency-based), Geographic (= geolocation), Multivalue, and Subnet. Health-checked endpoint monitoring gates them. It returns a CNAME/answer per policy, so it is still TTL-bound.
  • Azure Front Door — anycast L7 edge with health-based, near-instant failover without DNS TTL waits; pair with it (or use instead of Traffic Manager) when TTL-bound failover is too slow. Edge caching is content-delivery.

When to pick which

Host the zone in Azure DNS; alias the apex onto Front Door or Traffic Manager. Use Traffic Manager for DNS-level global routing across regions/clouds/on-prem; use Front Door when you need fast failover plus edge termination/caching.

Limits / things that bite (verify against current docs)

  • Traffic Manager is DNS-level → TTL-bound failover; Front Door is not.
  • Traffic Manager Performance routing uses an internet-latency table to Azure regions, keyed to the resolver — not the exact user.
  • Probe interval/timeout/tolerated-failures set detection speed; tighter = flap risk.
  • Per-profile endpoint counts and per-zone record-set quotas apply.

Pitfalls

  • Expecting Azure DNS alone to do failover/geo — that requires Traffic Manager or Front Door.
  • Confusing Traffic Manager (DNS, TTL-bound) with Front Door (anycast, fast) failover.
  • Nesting Traffic Manager profiles and losing track of effective TTL.

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