Remove dns infrastructure for sandbox routing

[sitole]

• Removed logic for DNS-based routing in client proxy
• Removes DNS server with legacy Redis backup storage
• Refactors use of sandbox routing catalog in api

---

Note

Removes DNS-based sandbox routing across API and client-proxy, replacing it with catalog-only resolution and cleaning up related config and dependencies.

• Backend/API:
  • Remove internal DNS server (packages/api/internal/dns/server.go) and DNS wiring in orchestrator; use SandboxesCatalog for StoreSandbox/DeleteSandbox.
  • Replace dns field with routingCatalog; stop starting/closing DNS server.
  • Dependencies: drop direct github.com/go-redis/cache/v9 and github.com/miekg/dns; tidy indirects in go.mod/go.sum.
• Client Proxy:
  • Eliminate DNS resolution; resolve sandboxes via catalog only in NewClientProxy and request handler.
  • Simplify NewClientProxy signature and usage; remove USE_CATALOG_RESOLUTION/USE_DNS_RESOLUTION env handling.
  • Remove DNS client logic and related imports.
• IaC:
  • Remove USE_CATALOG_RESOLUTION and USE_DNS_RESOLUTION env vars from iac/provider-gcp/nomad/jobs/edge.hcl.

^{Written by Cursor Bugbot for commit 3d6e4ab. This will update automatically on new commits. Configure here.}

[linear]

ENG-3137 Remove DNS infrastructure for sandbox routing

[sitole]

We can deploy this when all running sandboxes are registered in the Redis catalog.

Client proxy should be deployed first, so it will stop asking the DNS server if it is not found in the Redis catalog, but practically, the request will fail anyway, as it's not in the store, so a few milliseconds timeout will not be an issue here, and we can deploy in the same batch.

[jakubno]

😊