Summary

  • Quad9's profile of Darren Kara says the Principal Engineer helped clear a backlog of new resolver locations while a small team runs a network spread across hundreds of sites.
  • APNIC's interview and Quad9's data policy describe the boundary: reply addresses are transient, while coarse counters and limited threat feedback support operations.

The person adding a resolver site inherits every problem the site can have: a route that steers traffic badly, a server that answers slowly, a filter that misfires. Darren Kara's employer says he has been speeding up a backlog of points of presence. It also calls its engineering crew small and its anycast network global. That is a familiar infrastructure bargain: add doors for users, then keep each door working with the same pair of hands.

Kara's route to that job ran through three different custodians of Internet infrastructure. Quad9's staff account says he joined ARIN in 2000, helped stand up LACNIC and AFRINIC, and later operated ICANN's L-Root. Registry records, a root server and a public recursive resolver demand different kinds of evidence. At Quad9, a user's question reaches the resolver, but the service promises not to turn that visitor into a stored identifier.

That promise changes the debugging desk. In APNIC's October interview, Kara describes measurement built around aggregate data and anonymised source addresses. Information that could identify a user stays where it was collected. The published policy is more specific: the address needed to return a DNS answer remains in volatile memory for the transaction and is not copied into permanent storage. Counters can track the receiving site, a coarse BGP prefix and ASN, query type, response code, transport and filter status.

Those counters help an operator ask whether a new site is receiving traffic and whether a blocking feed is behaving as intended. They also create a second custody problem. Quad9 says counters can enter permanent archives; for a malicious domain supplied by an analyst, that analyst can receive count and timing feedback, possibly with selected dimensions. The operator's job is to know which summary crossed which boundary. APNIC says one supplier's intelligence must not leak to another.

The staff profile gives no site-by-site rollout ledger or measured before-and-after performance. The policy gives no fixed deletion date for those counters or partner-specific field schedule. A dated deployment register paired with a published field-and-retention schedule would let readers test both halves of Kara's task: whether the new doors work and what the network keeps while watching them.

Original records