Confirm
89
edits
Changes
Update Acknowledgements
0 - Off (default). use standard native resolving only (don't use TRR at all)
1 - Reserved (used to be Race (removedmode)
2 - First. Use TRR first, and only if the name resolve fails use the native resolver as a fallback.
3 - Only. Only use TRR. Never use the native (after the initial setup).
4 - Reserved (used to be Shadow. (removedmode)
5 - Off by choice. This is the same as 0 but marks it as done by choice and not done by default.
a couple of days. "localhost" and names in the ".local" TLD will never be
resolved via DOH.
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
to "example.com". TRR will also by default await the captive-portal detectionto raise its green flag before getting activated.
== See also ==
* Initial ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=1434852
* 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
