[ooni-dev] Understanding how client resolver is determined

[Khairil Yusof]

yaml webconnectivity log:

accessible: false
agent: redirect
blocking: dns
body_length_match: false
body_proportion: 0.09658116667249887
client_resolver: 202.188.1.6
control:
  dns:
    addrs: [sarawakreport.org, 104.25.9.14, 104.25.8.14]

Questions.

What is client_resolver how does it determine that it's 202.188.1.6, in
another yesterday it's 202.188.1.7 (https://explorer.ooni.torproject.or
g/measurement/20160802T205955Z_AS4788_3omRbM1JA9BYIMF5O5uiKEsdmUqy4kdun
nKn7exzBlM2ebboDh?input=http:%2F%2Fwww.sarawakreport.org)

Both of which I can't use to resolve addresses from the same network.

The system resolver in this case is 1.9.1.9. 202.188.1.5 would also
work but is not used in the report.

However the http_request does use the correct tampered address, so I'm
curious as to how it could use a resolver that I can't use to lookup
from the same network.