Where is DNS measured first?

From Santiago (SCL) toward Bogotá. A global average is not an SLO for letter D.

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.

DNS: timeouts in Santiago (SCL) · D-34

Runbook D-34 for DNS in Santiago (SCL). Marker xserv-d-42becb5b92ae. This page covers timeouts for LATAM operators, not a worldwide average.

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: A note on cost and transit

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 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.

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.