How fast is rollback for d-03?

The runbook is a command plus a named owner. There is no wait for a weekly change freeze.

Is transit the default path?

No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.

DNS: policy in Bogotá (BOG) · D-63

Runbook D-63 for DNS in Bogotá (BOG). Marker xserv-d-0da6bed283a0. This page covers policy for LATAM operators, not a worldwide average.

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: Failure modes we actually see

Capacity notes for d-04 assume rainy-season power in Miami and festival peaks toward São Paulo. The failure we actually see is a single uplink, not a cartoon partition of the whole continent. Spare ports and a second provider sit on the same runbook.

DNS: How this letter ties to the rest

Handoff from letter D DNS into the rest of the platform uses the same request IDs as the gateway. Runbook d-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

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.

DNS timeouts D-10

Timeouts on d-10 are tighter than the WAN RTT to Bogotá. DNS in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

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.