Trusted Recursive Resolver: Difference between revisions

Update Acknowledgements
(Updated the settings descriptions)
(Update Acknowledgements)
Line 13: Line 13:
  0 - Off (default). use standard native resolving only (don't use TRR at all)
  0 - Off (default). use standard native resolving only (don't use TRR at all)


  1 - Race (removed)
  1 - Reserved (used to be Race mode)


  2 - First. Use TRR first, and only if the name resolve fails use the native resolver as a fallback.
  2 - First. Use TRR first, and only if the name resolve fails use the native resolver as a fallback.
Line 19: Line 19:
  3 - Only. Only use TRR. Never use the native (after the initial setup).
  3 - Only. Only use TRR. Never use the native (after the initial setup).


  4 - Shadow. (removed)
  4 - Reserved (used to be Shadow mode)


  5 - Off by choice. This is the same as 0 but marks it as done by choice and not done by default.
  5 - Off by choice. This is the same as 0 but marks it as done by choice and not done by default.
Line 90: Line 90:
a couple of days. "localhost" and names in the ".local" TLD will never be
a couple of days. "localhost" and names in the ".local" TLD will never be
resolved via DOH.
resolved via DOH.


When TRR starts up, it will first verify that it works by first checking a
When TRR starts up, it will first verify that it works by first checking a
"confirmation" domain name. This confirmation domain is a pref by default set
"confirmation" domain name. This confirmation domain is a pref by default set
to "example.com". TRR will also by default await the captive-portal detection
to "example.com".
to raise its green flag before getting activated.


== See also ==
== See also ==
Line 101: Line 99:
* Initial ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=1434852
* Initial ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=1434852
* The DNS-over-HTTPS spec: https://tools.ietf.org/html/rfc8484
* The DNS-over-HTTPS spec: https://tools.ietf.org/html/rfc8484
== Acknowledgements ==
* [https://daniel.haxx.se/ Daniel Stenberg] wrote the initial implementation of TRR in Firefox
* [https://www.ducksong.com/ Patrick McManus] edited the RFC and reviewed the TRR code
Confirmed users
89

edits