Using HTTPS for Privacy Between DNS Stub and Recursive Resolvers

Document Type Replaced Internet-Draft (individual)
Author Paul Hoffman 
Last updated 2014-10-28 (latest revision 2014-10-22)
Replaced by draft-hoffman-dprive-dns-tls-https
Stream (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-hoffman-dprive-dns-tls-https
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


DNS queries and responses can contain information that reveals important information about the person who caused the queries, and it would be better if eavesdroppers were unable to see DNS traffic. This document describes how to use TLS for encrypting DNS traffic between a system acting as a DNS stub resolver and a system acting as a DNS recursive resolver. It defines how to easily wrap DNS queries in HTTP requests and interpret DNS responses in the HTTP respones; the HTTP here is always run under TLS on port 443. Discussion of this draft should take place in the DPRIVE WG.


Paul Hoffman (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)