the other DNS resolver can see your IP and the sites you look up if the route to it is not set to go through the VPN. you can maybe use something like traceroute to check that, but it should be possible to conclude it from the routing table.
Traceroute won’t show if you leak DNS requests outside of your VPN. (Unless you coincidentally also leak traffic, but then you’re pretty much just not using your VPN).
To confirm you’ll need to analyze your traffic-flow using a tool like tcpdump or Wireshark and check the source and destination for DNS traffic. If you see incoming DNS responses on an interface that is not your VPN-adaptor or maybe a loopback interface then you’re probably not tunnelling DNS through the VPN.
To answer the question in the headline: Regular DNS is unencrypted and quite easy to snoop on, so any node on the route between you and the DNS server will be able to read it if not using a VPN (i.e. DNS leak). Not sure what you mean by adversary, but it’s not like anyone on the internet can see your traffic. The DNS server may log your request and if you’re not on VPN, your IP address may be logged too.
My device is with always-on VPN and block connections without VPN on too, but I’d like to know if the DNS provider can see my real IP or the IP of VPN provider.
Appreciate the link but this doesn’t make me feel much better. Seems like their license and terms of use is basically, “Ask and we’ll tell you if you can do that.” Not very transparent.
Search for ET Legacy, which is what the project continuing development on the ET codebase is called, optimizing it for modern systems and sporting a sizeable community.
You can bind mount a directory on your pool into an lxc too. I do this with smb and a few other file/data services without issue but never tried omv. If containers work for you it might be the simpler way to go.
I have some notes from doing it but its been a minute, the overview is:
create your users in and out of the container with the correct ids
edit the conf to pass through the dir and map the ids
edit the subuid and subgid
The documentation on this kinda sucks because its not all in one place so if you find the first link you might get lost without the info in the second. I took me a few forum posts to find out about all the id mapping stuff and finally find the right page.
Because as long as it isn’t overwritten it can sometimes reside in a residual way in the storage sectors on the drive, these hdd scanning software’s check through the sectors for data hiding in them some sucxessfully some not as successfully, there for some will find more or less data than others do as well.
This is why data disappears on drives as well when a physical issue causes the sectors of the drive to begin to stop working aka “bad sectors” this makes the data start to seemingly magically vanish or corrupt if it’s still operating and booting into Windows you can at times witness the data/folders and or files present in folders one moment and missing fron the OS the next, that’s an indictator often of an imminent drive failure due to bad sectors. In this scenario it get’s less likely you’ll recover the data the longer the drive is in use because more of the sectors will probably die. You want to be doing the recovery and not using the drive in Windows in this instance. I say Windows but it applies to any HDD with any OS installed really.
I run snapraid and mergerfs, as the nas storage. Not much changes on my NAS and the stuff I really care about like my pictures and videos are on a small ZFS pool. Both are directly on proxmox, meaning I can just plug them in to another Linux machine and research if it all goes sideways. Its all shared from the host via SMB NFS or for jellyfin and immicher its a moint point for the container
kbin.life
Oldest