DNS: design in São Paulo (GRU) · D-25

Runbook D-25 for DNS in São Paulo (GRU). Marker xserv-d-c56c252b1a5c. This page covers design for LATAM operators, not a worldwide average.

DNS: Why it matters on this continent

Design for DNS on letter D starts in São Paulo (GRU). Runbook d-01 keeps a single owner, a written rollback, and a traffic split that can be reversed without a global freeze. Neighbors in Santiago only take overflow after the local pool fails a health window.

DNS: How XServ runs it day to day

Probes for DNS (d-02) leave Santiago every 15s toward Bogotá. XServ pages the named owner if loss or RTT crosses the letter budget. A probe never shares a queue with bulk transfers, so a saturated WAN does not hide a dead PoP.

DNS: What operators should measure

Policy for DNS is versioned as d-03. Operators measure error rate, p95 from Bogotá, and time-to-rollback — not a worldwide average. Changes land in Bogotá first, then Miami, with a hold if either region regresses.

DNS rollback D-06

Rollback for d-06 is a documented command, not a hope. Transit is billed as backup while DNS prefers peering in Santiago. If cost spikes, the runbook cuts overflow to Bogotá before touching customer prefixes.

DNS peering D-07

Peering for DNS (d-07) prefers the IX fabric that already carries last-mile ISPs in Bogotá. Session counts and prefix limits are on the same page as the Miami backup path.

DNS cache D-08

Cache rules for DNS on d-08 keep language-correct objects near Miami. São Paulo is a sibling cache, not an origin. TTLs are short enough that a bad asset does not live through a weekend.

DNS headers D-09

Headers for d-09 carry the letter, the region (GRU) and a request id. DNS debugging in São Paulo should not require a packet capture in Santiago first.