Does DNS on letter D share fate with other letters?

The control plane is shared. Data-plane queues for DNS stay isolated, so incident d-01 cannot drain neighbor letters.

Where is DNS measured first?

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

DNS: handoff in São Paulo (GRU) · D-53

Runbook D-53 for DNS in São Paulo (GRU). Marker xserv-d-588500e318be. This page covers handoff for LATAM operators, not a worldwide average.

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

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.