Yeah, did that. Couldn’t DNS-resolve the website because of the issue, but going via direct IP of the “check-website” (found via who.is) made me at least check my IP, which turned out to be the VPN-IP. Torrent-IP-Checking won’t work, because torrents seem to need at least DNS-resolving at the beginning of download.
Yeah, it may be good. Unfortunately unpredictable things can happen…
It may not be ideal for torrenting, but it works for me I think. Maybe that’s a topic for another thread.
I guess I can rule that one out. FF has DNS-over-HTTPS but it’s turned off. The DNS from Mullvad is usually used in my case…
I understand the basic concept of DNS but I am just a little unsure in which part of the process it takes effect. Thanks for your point of view!
Yeah, I will investigate it further. Do you have similar issues?
Interesting!
So if I get it right: Only when starting a torrent, some DNS needs to be resolved? And when the torrent is already running not?
So in my case a possible DNS leak occurs somewhere in the middle of the night. Not right from the beginning.
Thought so too. As described above, I tried pinging 8.8.8.8., which worked out. Didn’t try reaching 8.8.8.8. via browser though.
I also have an alternative privacy-friendly DNS set up in my router. Not sure, if that can be a problem. Normally, the DNS of Mullvad is used.
But another question is: Could that be a privacy-risk? Torrenting works without DNS-resolving, doesn’t it?
Yeah, I tried that with disconnecting and the torrents stopped immediately, which is good.
Just wondering, why I cannot open any websites in the morning, while the torrents are still working…leaves a bad feeling, but maybe I’m also overreacting about this.
I am using the normal version of firefox.
I am currently not aware of a (torrent) leak-checking method, without using the browser. How would be your approach?
And Mullvad is very good with its killswitches.
Yeah, I heard good things about it. Just wanting to make sure, things are going well.
Let’s say the torrent started with a working DNS and the issue occured some hours later. Maybe the client wants to check for IP-updates then, but won’t find any, because DNS doesn’t work anymore. It will still keep the IP-adresses resolved at the beginning, right? Because then it would make sense, that I saw some working torrents, even though the issue already appeared.