how does DNS over TLS help with privacy? please explain it to me, since the ISP can still see the IP your sending data to and getting data from and can just reverse DNS lookup that IP
With plain DNS the ISP can see that you request example.tld to 1.1.1.1
With encrypted DNS (DoT, DoH, DoQ, DNSCrypt…) the requests are encrypted with TLS or other, o only see that you connected to dns.cloudflare.com not the domain that you request, so it cannot see that you requested example.tld
ISPs can always see what domains you visit due to it being leaked in plain text via the SNI portion of the Client Hello sequence of establishing a TLS connection to a web server, whether your DNS requests are encrypted or not.
It’s important to remember that using encrypted DNS does not shield the domains names you visit from your ISP. I feel this is a fundamental misunderstanding that gives some a false sense of privacy. At best, from a privacy perspective, you might avoid DNS-based logging which are slightly more trivial to log than domain taken from SNI.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !privacyguides@lemmy.one
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We’ve tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the “official” Privacy Guides community on Lemmy, which can be verified here. Other “Privacy Guides” communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
We prefer posting about open-source software whenever possible.
No soliciting engagement: Don’t ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don’t repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
use dns-over-tls if you want privacy.
also only domains are exposed in plain text.
how does DNS over TLS help with privacy? please explain it to me, since the ISP can still see the IP your sending data to and getting data from and can just reverse DNS lookup that IP
With plain DNS the ISP can see that you request example.tld to 1.1.1.1
With encrypted DNS (DoT, DoH, DoQ, DNSCrypt…) the requests are encrypted with TLS or other, o only see that you connected to dns.cloudflare.com not the domain that you request, so it cannot see that you requested example.tld
ISPs can always see what domains you visit due to it being leaked in plain text via the SNI portion of the Client Hello sequence of establishing a TLS connection to a web server, whether your DNS requests are encrypted or not.
It’s important to remember that using encrypted DNS does not shield the domains names you visit from your ISP. I feel this is a fundamental misunderstanding that gives some a false sense of privacy. At best, from a privacy perspective, you might avoid DNS-based logging which are slightly more trivial to log than domain taken from SNI.
isp can still see the ip, but it’s not as big of an issue as plain domain names (because the default dns logs requests 90% of the time).
I’m fairly certain that’s not how it works, you’re describing a VPN where your isp routes all traffic to an IP
Almost, but only for DNS https://heimdalsecurity.com/blog/what-is-encrypted-dns-traffic/
You can also use DNS-over-SSH or DNS-over-TOR, only tunnels the DNS not the whole traffic