[Autogenerated] Since we're talking about
the client and DNA Jest, I'd like to bring
up DNA's privacy. As we've seen in wire
Shark. The name of each server that we
query for is in clear text. Indiana's
Palmach API tras designed the DNAs
Protocol. He moved us from manually
updated host files to the scalable
distributed DNA system we still use today,
However, just like other protocols of its
time, it was in clear text. The first are
of C for DNA's was published November of
87 and the protocol was still in clear
text. What if someone spoofs the IP
address of your DNA server and starts
logging everywhere? You want to go or
worse, send you a fake site and steals all
of the information you give when you make
a purchase? Dina SQL supposed to fix that
by building a chain of certificates from
the root server down to the authoritative
server. So you knew who you were talking
to. Problem was, it was all clear. Text.
Edward Snowden's release of government
documents publicized the rampant passive
surveillance that was happening, including
DNA's info. This lit a fire in the
community to implement privacy within DNS
and DNA's over teal us or do t was born do
t runs on port 8 53 making it easy to
block these unique port number. The only
encrypted connection is between the client
and their resolve. Er, the connections.
The resolve, er makes are all clear text.
There's also no native implementations for
Windows, macOS or IOS, so it didn't gain
popularity. Having to installed special
software to use your own client as a stub
resolve er doesn't really appeal to many
people. P s a stub resolve er is just
another name for the DNAs process on a
client. Also, the resolve er has to be
capable of do t. There's a list on DNS
privacy dot org's I put a link in your
exercise document in 2018. The RFC for DNS
over https or DOE was published with dough
just like do T. We'd use an outside
server, not our normal resolve. Er, the
traffic from our client through the ISP to
the Dough server runs on Port 443 so the
ISP can't used ness to track us. However,
only the connection between the client and
their resolve, er, is encrypted
connections made by the resolve er are
still in clear text. The resolve er and
the upstream DNA servers could still track
the resolved names. Dokan take advantage
of the web apps already in place to gain
efficiency, but that doesn't help privacy.
You'll have to modify the browser settings
and use a doe enabled server such as
Google or Cloudflare, but at least you
don't have to use an internal study resolved.