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

Runbook D-73 for DNS in São Paulo (GRU). Marker xserv-d-85b109cba1ff. 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 regions D-11

Region names on d-11 match DNS and tickets: Bogotá / BOG, with Miami as the documented pair. DNS dashboards never say “LATAM” as if it were one RTT.

DNS docs D-12

Public docs for letter D stay aligned with identifier xserv-d-pack. Page d-12 is the DNS slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.

DNS design D-01

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 probe D-02

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.