It doesn't look like you're using protonDNS. Check out this: https://www.reddit.com/r/pihole/comments/pdmspf/pihole_with_protonvpn/ It looks like you need to enable DNS-over-https or DNS-over-TLS? Maybe cloudflared would help? There are instructions for installing it on a pihole
On Tue, Feb 18, 2025 at 4:09 PM American Citizen <[email protected]> wrote: > Hello All: > > I am trying to establish a secure internet connection using a vpn config > connections file (protonvpn) > > While the initial connection shows that I am only using ProtonVPN's DNS > resolvers, after a period of time things degenerate. > > Here's is the log file (I apologize for the length) from > https://www.dnscheck.tools after I let my connection be established for > around 90 mins or so. > > > > > dnscheck.tools <https://www.dnscheck.tools/> > > > > Results <https://www.dnscheck.tools/#> About > > <https://www.dnscheck.tools/#more> > > > > Hello! Your public IP addresses are: > > GLOBALAXS-MNT > > > > * 146.70.230.149 <https://info.addr.tools/146.70.230.149> ns: > > a.ns.ns247.net Los Angeles, California, US > > > > Your DNS resolvers specify your IP subnet (ECS > > <https://en.wikipedia.org/wiki/EDNS_Client_Subnet>): > > GLOBALAXS-MNT > > > > * 146.70.230.0/24 <https://info.addr.tools/146.70.230.0/24>Los > > Angeles, California, US > > > > Your DNS resolvers are: > > Cloudflare > > > > * 172.70.205.166 <https://info.addr.tools/172.70.205.166> ns: > > cruz.ns.cloudflare.com Los Angeles, California, US > > * 172.70.205.167 <https://info.addr.tools/172.70.205.167> ns: > > cruz.ns.cloudflare.com Los Angeles, California, US > > * 172.70.209.36 <https://info.addr.tools/172.70.209.36> ns: > > cruz.ns.cloudflare.com Los Angeles, California, US > > * 172.70.209.38 <https://info.addr.tools/172.70.209.38> ns: > > cruz.ns.cloudflare.com Los Angeles, California, US > > * 172.70.209.39 <https://info.addr.tools/172.70.209.39> ns: > > cruz.ns.cloudflare.com Los Angeles, California, US > > * 172.70.213.18 <https://info.addr.tools/172.70.213.18> ns: > > cruz.ns.cloudflare.com Los Angeles, California, US > > * 172.70.213.161 <https://info.addr.tools/172.70.213.161> ns: > > cruz.ns.cloudflare.com Los Angeles, California, US > > > > CLOUDFLARE_2400_CB00_0000_36 > > > > * 2400:cb00:12:1024::ac45:20d3 > > <https://info.addr.tools/2400:cb00:12:1024::ac45:20d3> ns: > > chloe.ns.cloudflare.com Los Angeles, California, US > > * 2400:cb00:12:1024::ac45:20d4 > > <https://info.addr.tools/2400:cb00:12:1024::ac45:20d4> ns: > > chloe.ns.cloudflare.com Los Angeles, California, US > > * 2400:cb00:445:1024::ac46:cda6 > > <https://info.addr.tools/2400:cb00:445:1024::ac46:cda6> ns: > > chloe.ns.cloudflare.com Los Angeles, California, US > > * 2400:cb00:445:1024::ac46:cda7 > > <https://info.addr.tools/2400:cb00:445:1024::ac46:cda7> ns: > > chloe.ns.cloudflare.com Los Angeles, California, US > > * 2400:cb00:446:1024::ac46:d126 > > <https://info.addr.tools/2400:cb00:446:1024::ac46:d126> ns: > > chloe.ns.cloudflare.com Los Angeles, California, US > > * 2400:cb00:446:1024::ac46:d127 > > <https://info.addr.tools/2400:cb00:446:1024::ac46:d127> ns: > > chloe.ns.cloudflare.com Los Angeles, California, US > > * 2400:cb00:447:1024::ac46:d512 > > <https://info.addr.tools/2400:cb00:447:1024::ac46:d512> ns: > > chloe.ns.cloudflare.com Los Angeles, California, US > > * 2400:cb00:447:1024::ac46:d5a1 > > <https://info.addr.tools/2400:cb00:447:1024::ac46:d5a1> ns: > > chloe.ns.cloudflare.com Los Angeles, California, US > > > > GLOBALAXS-MNT > > > > * 146.70.230.147 <https://info.addr.tools/146.70.230.147> ns: > > a.ns.ns247.net Los Angeles, California, US > > * 146.70.230.148 <https://info.addr.tools/146.70.230.148> ns: > > a.ns.ns247.net Los Angeles, California, US > > * 146.70.230.149 <https://info.addr.tools/146.70.230.149> ns: > > a.ns.ns247.net Los Angeles, California, US > > * 146.70.230.150 <https://info.addr.tools/146.70.230.150> ns: > > a.ns.ns247.net Los Angeles, California, US > > * 2a0d:5600:4f:23::11 <https://info.addr.tools/2a0d:5600:4f:23::11> > > ns: pri.authdns.ripe.net Los Angeles, California, US > > * 2a0d:5600:4f:23::12 <https://info.addr.tools/2a0d:5600:4f:23::12> > > ns: pri.authdns.ripe.net Los Angeles, California, US > > * 2a0d:5600:4f:23::13 <https://info.addr.tools/2a0d:5600:4f:23::13> > > ns: pri.authdns.ripe.net Los Angeles, California, US > > * 2a0d:5600:4f:23::14 <https://info.addr.tools/2a0d:5600:4f:23::14> > > ns: pri.authdns.ripe.net Los Angeles, California, US > > > > Google > > > > * 74.125.181.144 <https://info.addr.tools/74.125.181.144> ns: > > ns1.google.com Los Angeles, California, US > > * 74.125.181.146 <https://info.addr.tools/74.125.181.146> ns: > > ns1.google.com Los Angeles, California, US > > * 74.125.181.147 <https://info.addr.tools/74.125.181.147> ns: > > ns1.google.com Los Angeles, California, US > > * 74.125.181.148 <https://info.addr.tools/74.125.181.148> ns: > > ns1.google.com Los Angeles, California, US > > * 74.125.181.149 <https://info.addr.tools/74.125.181.149> ns: > > ns1.google.com Los Angeles, California, US > > * 74.125.181.150 <https://info.addr.tools/74.125.181.150> ns: > > ns1.google.com Los Angeles, California, US > > * 74.125.181.151 <https://info.addr.tools/74.125.181.151> ns: > > ns1.google.com Los Angeles, California, US > > * 74.125.181.152 <https://info.addr.tools/74.125.181.152> ns: > > ns1.google.com Los Angeles, California, US > > * 74.125.181.153 <https://info.addr.tools/74.125.181.153> ns: > > ns1.google.com Los Angeles, California, US > > * 74.125.181.154 <https://info.addr.tools/74.125.181.154> ns: > > ns1.google.com Los Angeles, California, US > > * 74.125.181.155 <https://info.addr.tools/74.125.181.155> ns: > > ns1.google.com Los Angeles, California, US > > * 74.125.181.157 <https://info.addr.tools/74.125.181.157> ns: > > ns1.google.com Los Angeles, California, US > > * 74.125.181.158 <https://info.addr.tools/74.125.181.158> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.16 <https://info.addr.tools/172.253.0.16> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.17 <https://info.addr.tools/172.253.0.17> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.18 <https://info.addr.tools/172.253.0.18> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.19 <https://info.addr.tools/172.253.0.19> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.20 <https://info.addr.tools/172.253.0.20> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.21 <https://info.addr.tools/172.253.0.21> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.22 <https://info.addr.tools/172.253.0.22> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.23 <https://info.addr.tools/172.253.0.23> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.24 <https://info.addr.tools/172.253.0.24> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.26 <https://info.addr.tools/172.253.0.26> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.27 <https://info.addr.tools/172.253.0.27> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.28 <https://info.addr.tools/172.253.0.28> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.29 <https://info.addr.tools/172.253.0.29> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.0.30 <https://info.addr.tools/172.253.0.30> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.16 <https://info.addr.tools/172.253.1.16> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.17 <https://info.addr.tools/172.253.1.17> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.18 <https://info.addr.tools/172.253.1.18> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.19 <https://info.addr.tools/172.253.1.19> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.21 <https://info.addr.tools/172.253.1.21> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.22 <https://info.addr.tools/172.253.1.22> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.23 <https://info.addr.tools/172.253.1.23> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.24 <https://info.addr.tools/172.253.1.24> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.25 <https://info.addr.tools/172.253.1.25> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.26 <https://info.addr.tools/172.253.1.26> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.27 <https://info.addr.tools/172.253.1.27> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.28 <https://info.addr.tools/172.253.1.28> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.29 <https://info.addr.tools/172.253.1.29> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.1.30 <https://info.addr.tools/172.253.1.30> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.2.24 <https://info.addr.tools/172.253.2.24> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.9.212 <https://info.addr.tools/172.253.9.212> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.9.213 <https://info.addr.tools/172.253.9.213> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.9.214 <https://info.addr.tools/172.253.9.214> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.9.215 <https://info.addr.tools/172.253.9.215> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.9.216 <https://info.addr.tools/172.253.9.216> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.9.217 <https://info.addr.tools/172.253.9.217> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.9.218 <https://info.addr.tools/172.253.9.218> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.9.220 <https://info.addr.tools/172.253.9.220> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.9.221 <https://info.addr.tools/172.253.9.221> ns: > > ns1.google.com Los Angeles, California, US > > * 172.253.9.222 <https://info.addr.tools/172.253.9.222> ns: > > ns1.google.com Los Angeles, California, US > > * 2607:f8b0:4004:1000::123 > > <https://info.addr.tools/2607:f8b0:4004:1000::123> ns: > > ns1.google.com Los Angeles, California, US > > * 2607:f8b0:4004:1000::124 > > <https://info.addr.tools/2607:f8b0:4004:1000::124> ns: > > ns1.google.com Los Angeles, California, US > > * 2607:f8b0:4004:1000::129 > > <https://info.addr.tools/2607:f8b0:4004:1000::129> ns: > > ns1.google.com Los Angeles, California, US > > * 2607:f8b0:4004:1007::123 > > <https://info.addr.tools/2607:f8b0:4004:1007::123> ns: > > ns1.google.com Los Angeles, California, US > > > > Great! Your DNS responses are authenticated with DNSSEC > > <https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions>: > > > > ECDSA P-256 ECDSA P-384 Ed25519 > > Good signature ✓ ✓ ✓ > > Bad signature ✓ ✓ ✓ > > Expired signature ✓ ✓ ✓ > > Missing signature ✓ ✓ ✓ > > > > See more tools at addr.tools <https://www.addr.tools/> > > I want to ask the Linux community the question, how can we secure our > sessions and not have DNS leakage? > > I don't want to have my DNS queries be logged. > > This is a disappointment to me, to find the gradual incursion of other > DNS servers into my internet session. (or network session) > > How can we establish a truly secure internet session with controlled DNS > lookups? > > Randall > > > > >
