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.

referencesprovidersgeneric.md

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

DNS — generic / self-hosted

The vendor-neutral default. When no cloud is named, this is the answer.

What to run

  • BIND — the reference authoritative + recursive server; ubiquitous, flexible, zone-file driven. Heaviest to operate; large attack surface if misconfigured.
  • PowerDNS — authoritative server with pluggable backends (SQL, etc.) plus a separate recursor; good when zones live in a database. Some geo/load features via backends (e.g. geoip).
  • Knot DNS / NSD — modern, fast authoritative-only servers; pair with Unbound as the recursive resolver. Common for high-performance authoritative tiers.
  • CoreDNS — plugin-based, common inside Kubernetes for service discovery.

Topology

  • Authoritative tier holds your zones; run at least two name servers, on separate networks/sites. Standard DNS supports primary→secondary zone transfer (AXFR/IXFR) so secondaries stay in sync — use it for redundancy.
  • Anycast the authoritative IPs across sites via BGP for proximity and DDoS resilience (you operate the routing).
  • Recursive resolvers are usually the client's/ISP's; you run recursors only for internal resolution.

Routing policies without a managed service

Plain BIND/NSD give you simple and round-robin (multiple A records) out of the box. Weighted, latency, geo, and failover policies are features layered on top — PowerDNS geoip/lua backends, dnsdist, or a GSLB appliance — and health- checked failover means running your own prober that rewrites zone records on failure. This operational burden is exactly why most teams use a managed provider for traffic steering.

Limits / things that bite

  • Self-run health-check failover is DIY: you build the prober, the thresholds, and the record-rewrite path — and it's still TTL-bound for recovery.
  • Zone transfers must be secured (TSIG) or you leak/expose your zone.
  • A misconfigured open recursive resolver becomes a DDoS amplifier — lock it down.
  • Geo/latency steering needs an IP-geolocation database you keep current.

Pitfalls

  • One physical site for all authoritative servers → SPOF; spread them.
  • Forgetting DNSSEC key rollover if signing zones (broken validation = outage).
  • Treating round-robin A records as load balancing — clients cache one answer and there's no health awareness.

Maximum control and zero lock-in, but you own anycast/BGP, health checking, and geo data. Use when running your own infra or when a managed provider can't meet a constraint; otherwise a managed zone removes most of this toil.

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