home.social

#dnsleak — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #dnsleak, aggregated by home.social.

fetched live
  1. Ayudando a una persona cercana a configurar su conexión con VPN.

    Hemos descubierto que tiene un #dnsleak porque la página dnsleaktest.com no es resuelta por los DNS de su ISP - DIGI para más señas.

    Configurando un DNS seguro desde el navegador puede acceder sin problemas, pero aquí el leak no es revelado.

    Le he dicho que quite el router de su ISP y mejor ponemos un router neutro. Voy a tener tarea...

  2. After setting up DNS over HTTPS, got curious how DNS leak test tools, which discover your DNS resolver, such as Browser Leaks, work :blobcatthinking:

    Turns out, it's quite clever setup: while you are visiting browserleaks.com website, in the background it queries a number of hostnames generated especially for you, such as 9d0pafrc5tnu.dns4.browserleaks.net, 0zfannouveb4.dns4.browserleaks.org and so on.

    Because the website generates those hostnames specifically for your session, it is able to associate your external IP to the hostnames you attempt to resolve.

    Now because site operators controls authoritative name servers behind those generated hostnames - specifically ns2.browserleaks.net and ns1.browserleaks.net (also with .org), from logs they can check what exact DNS resolver asked for those unique hostnames.

    Simply matching a resolver DNS that attempted to resolve those unique hostnames is enough to link it to your visit of a website session - it is often going to be the resolver of your internet service or virtual private network provider, unless you've explicitly changed your resolver to something else. Still, easily visible to authoritative DNS server.

    Voila! No magic, just simple, nice setup :blobcatcheer:

    Just think of how many fingerprinting schemes can big techs carry out to track you across the internet with vast compute resources available to them... :blobcatheadinitshands:

    #itsalwaysdns #dns #resolver #dnsleak #survelliance #tracking #privacy

  3. DNS leak protection is a security feature in VPNs that forces all web browsing queries (DNS requests) through an encrypted VPN tunnel, preventing them from being exposed to your Internet Service Provider (ISP). It prevents hackers or ISPs from seeing your browsing history and location, ensuring your traffic stays private and secure. windows101tricks.com/what-is-d

    What is DNS leak protection? It’s a VPN feature that keeps your DNS requests inside the encrypted VPN tunnel and away from your ISP’s DNS servers.

    What is a DNS leak in VPN? It’s when your DNS queries escape the VPN tunnel and go to your ISP’s DNS servers, revealing the websites you visit.

    How DNS leak protection works: It routes all DNS traffic through VPN DNS servers, blocks DNS outside the tunnel, and may use firewall rules and a kill switch.

    How to test DNS leak in VPN: Connect to your VPN, visit a DNS leak test website, run a test, and check if the DNS servers match your VPN server location.

    Does VPN prevent DNS leaks? Only if the VPN is designed with proper DNS leak protection and configured correctly.

    @followers #VPN #DNS #security #Tech #privacy #DNSLeak

  4. Stupid NetworkManager insists on overwriting /etc/resolv.conf... Me making the file not writable should do it dammit...

    dns = none in /etc/NetworkManager/NetworkManager.conf gives..
    "NetworkManager.service: Start request repeated too quickly"

    #dnsleak #NetworkManager

  5. @danslerush

    It would be great if when someone reports a #DNSLeak on Fediverse that is related to #TorProject, that someone at TorProject might pick it up.

    See our boosted toot. We've been boosting for half a month now.

    @torproject