Content deleted Content added
Citation bot (talk | contribs) Add: newspaper. | Use this bot. Report bugs. | Suggested by AManWithNoPlan | #UCB_toolbar Tags: Manual revert Reverted |
Restored revision 1154800530 by AManWithNoPlan (talk) |
||
Line 58:
| last2 = Surý
| first2 = Ondřej
| doi = 10.17487/RFC8624
| s2cid = 195856691
Line 104 ⟶ 103:
| last2 = Sury
| first2 = O.
| s2cid = 195856691
}}</ref>
Line 153 ⟶ 151:
| last5= Arends
| first5= Roy
| doi= 10.17487/RFC4033
}}
Line 173 ⟶ 170:
A ''validating stub resolver'' can also potentially perform its own signature validation by setting the Checking Disabled (CD) bit in its query messages.<ref name="rfc4033_p12"/> A validating stub resolver uses the CD bit to perform its own recursive authentication. Using such a validating stub resolver gives the client end-to-end DNS security for domains implementing DNSSEC, even if the Internet service provider or the connection to them is not trusted.
Non-validating stub resolvers must rely on external DNSSEC validation services, such as those controlled by the user's [[Internet service provider]] or a [[public recursive name server]], and the communication channels between itself and those name servers, using methods such as [[DNS over TLS]].<ref name="rfc4033_p12">{{Cite journal | title= RFC 4033: DNS Security Introduction and Requirements | publisher= [[The Internet Society]] | date= March 2005 | page= 12 | url= http://tools.ietf.org/html/rfc4033#page-12 | last1= Rose | first1= Scott | last2= Larson | first2= Matt | last3= Massey | first3= Dan | last4= Austein | first4= Rob | last5= Arends | first5= Roy
===Trust anchors and authentication chains===
|