From 5008042079cfa0ebaa255c58a9447d2b67cd76d8 Mon Sep 17 00:00:00 2001
From: mfwmyfacewhen <94880365+mfwmyfacewhen@users.noreply.github.com>
Date: Fri, 19 May 2023 17:40:37 -0500
Subject: [PATCH] add odoh

---
 docs/basics/vpn-overview.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/basics/vpn-overview.md b/docs/basics/vpn-overview.md
index a3aec23b..18333891 100644
--- a/docs/basics/vpn-overview.md
+++ b/docs/basics/vpn-overview.md
@@ -89,6 +89,8 @@ Multi-Party Relays use multiple nodes owned by different parties, such that no i
 
 MPRs seek to solve a problem inherent to VPNs: the fact that you must trust them completely.
 
+MPRs typically have ways of protecting your DNS traffic. Apple's Private Relay uses ODoH, INVISV uses Obvlivious DNS, and Tor lets the exit node do the DNS lookup for you.
+
 ## Decentralized VPNs
 
 Another attempt at solving the issues with centralized VPN services are dVPNs. These are based on blockchain technology and claim to eliminiate trust in a single party by distributing the nodes across lots of different people. However, many times a dVPN will default to a single node, meaning you need to trust that node completely, just like a traditional VPN. Unlike a traditional VPN, this one node that can see all your traffic is a random person instead of your VPN provider that can be audited and has legal responsiblities to uphold their privacy policy. Multi-hop is needed to solve this, but that comes with a stability and performance cost.