← ClaudeAtlas

hybrid-connectivity-dns-desklisted

design hybrid connectivity and dns, covering dedicated circuits and encrypted tunnels with genuinely diverse redundant paths, bgp route exchange and failover behavior including degraded-bandwidth backup, on-premises address overlap resolution, dns zone architecture across the hybrid boundary with split-horizon resolution forwarders and resolver endpoints, certificate ownership and renewal, and global traffic distribution with health checks and ttl behavior. use for direct circuit design, vpn failover, bgp routing, hybrid dns, split-horizon zones, certificate lifecycle, and latency or geo traffic steering.
MadewellRD/skills-lab · ★ 2 · AI & Automation · score 65
Install: claude install-skill MadewellRD/skills-lab
# Hybrid Connectivity DNS Desk ## Suite workflow mode This desk is a member of the Cloud Infrastructure Command Desk suite. Complete the connectivity artifact set, update the `infrastructure_packet`, and continue to the next stage whenever available source facts support it. The packet shape and the continuity rule live in `references/suite-workflow-contract.md`; this stage's input and output boundary is in `references/stage-contracts.md`. Return `Workflow Halt` only for one of the six hard classes: missing approval, production or destructive action, security or privacy exposure, genuine source conflict, release integrity asserted without evidence, or an unreachable connector. Never invent circuit identifiers, virtual interface or VLAN tags, autonomous system numbers, advertised prefixes, peer addresses, colocation facility names, bandwidth figures, DNS record contents, zone names, resolver endpoint addresses, certificate authorities, or expiry dates. ## Role Own the boundary crossing. This desk designs dedicated circuits and encrypted tunnels with their redundancy, the route exchange between the cloud estate and everything outside it including what happens when the primary path drops, the resolution of on-premises address overlap, the DNS zone architecture across the hybrid boundary including split-horizon views, forwarding, and resolver placement, certificate and name ownership, global traffic distribution where the workload needs it, and the connectivity failure modes