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.

referencesprovidersgcp.md

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

DNS — GCP

Service mapping

GCP also splits zone hosting from global steering — most traffic steering happens in the load balancer, not in Cloud DNS.

  • Cloud DNS — managed authoritative hosting on Google's anycast network. Public and private zones, standard record types, DNSSEC, and routing policies: Weighted round-robin and Geolocation (answer by client region), plus health-checked failover for internal/private routing. Apex support is via the policy/record set rather than a separate alias type — point records at a global LB IP.
  • Cloud Load Balancing (global external) — the primary "latency/geo" steerer. A single anycast global IP front-ends all regions; Google's edge routes users to the nearest healthy backend and fails over without DNS TTL waits. Prefer this over DNS-level geo for speed and fast failover. Edge caching (Cloud CDN) is content-delivery.
  • Cloud DNS routing policies cover DNS-level weighted/geo when you specifically need answers to differ per client rather than a single anycast IP.

When to pick which

Default: one global external Application LB on an anycast IP, with Cloud DNS holding a simple record pointing at it — proximity and failover handled at the LB, no TTL dependency. Reach for Cloud DNS geolocation/weighted policies when you need the answer itself to differ (data residency, canary across distinct IPs).

Limits / things that bite (verify against current docs)

  • DNS-level geo/weighted policies are TTL-bound; the global LB's anycast steering is not.
  • Cloud DNS geolocation maps by client region (resolver-influenced), not exact user.
  • Per-zone record-set and per-policy item quotas apply.
  • Health-checked DNS failover applies mainly to private/internal zones — public fast failover is the LB's job.

Pitfalls

  • Building DNS-level geo routing when a single global anycast LB IP would be simpler and faster.
  • Forgetting DNSSEC key management once enabled (validation breaks = outage).
  • Assuming Cloud DNS does latency routing like a managed competitor — favor the LB instead.

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