What problem does it solve? It clarifies when DNS records actually need to be created in a zipbox sandbox and provides the exact CLI commands to pin, list, or delete records without touching zone files or provider APIs. ## Core Features & Use Cases - Wildcard-first guidance: Explains that every name under the sandbox apex already resolves via a platform wildcard, so serving a subdomain requires no DNS work at all. - Explicit record management: Uses the baked tribes-dns CLI to set A (IPv4-only) or AAAA (IPv6-only) records, expose both stacks, list records, and delete them. - Safety guardrails: Documents reserved system names, apex protection, record quotas (30 records, 10 mutations/minute), and the need to re-expose records after a restore or host move. - Use Case: You want api.hish.zipbox.ai to answer over IPv6 only. Run tribes-dns set api AAAA to pin the name to the sandbox's guest IPv6, overriding the wildcard for that exact name. ## Quick Start Ask the agent to list current DNS records with tribes-dns, or to pin a subdomain like api to a single stack using the tribes-dns set command.