tree: d665364f842cd86b79b44f091290f7366b2833b3 [path history] [tgz]
  1. init/
  2. seccomp/
  3. ares_client.cc
  4. ares_client.h
  5. ares_client_fuzzer.cc
  6. BUILD.gn
  7. chrome_features_service_client.cc
  8. chrome_features_service_client.h
  9. controller.cc
  10. controller.h
  11. doh_curl_client.cc
  12. doh_curl_client.h
  13. doh_curl_client_fuzzer.cc
  14. main.cc
  15. metrics.cc
  16. metrics.h
  17. OWNERS
  18. proxy.cc
  19. proxy.h
  20. proxy_test.cc
  21. README.md
  22. resolver.cc
  23. resolver.h
  24. resolver_fuzzer.cc
  25. resolver_test.cc
  26. session_monitor.cc
  27. session_monitor.h
dns-proxy/README.md

dns-proxy

This directory contains the DNS proxy service that is used to support DNS proxying for VPNs and provide DNS-over-HTTPS functionality for Chrome OS and virtualized guest OSes.

The dns-proxy controller is responsible for managing the lifecycles of the child proxy processes. On start, it launches the system and default network proxies and, as needed, for ARC.

Each child process provides both standard plain-text as well as DNS-over-HTTPS name resolution functionality and relies on Chrome‘s Secure DNS settings to configure its behavior. The system proxy relays DNS traffic for system processes. It always tracks the default (highest priority) physical network; and will ignore any VPN running on the host or inside ARC, if applicable. The default network proxy will always track the highest priority network, including VPNs. Each ARC proxy is bound to a single ARC bridge interface (excluding the control bridge), which allows interface-aware Android applications to use DoH via the proxy. Chrome’s DNS traffic is ignored and never proxied.