Yes and no; while the second hop (recursive resolver) won't know the client's IP/geo, we've chosen to locate the first and second hops very near each other in t

Yes and no; while the second hop (recursive resolver) won't know the client's IP/geo, we've chosen to locate the first and second hops very near each other in terms of network latency and, eventually, to roll out enough first hops so that there won't be much (region-scale) geographic distance between the client, the first hop, and the second hop. This would require a slight modification to the existing mechanism. (A client could include ECS as is, but it'd be bad for their privacy.)