New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Why would you want that? The fact that your DNS is different from your gateway IP doesn't mean that it's leaking.
For example, I took the test and it tries to scare me like this just because I'm using OpenDNS:
@Nyr I'm just curious how they achieve that. Currently I installed pi-hole on the VPN server, and dnsleaktest indeed show the upstream DNS (Google/Cloudflare)
By running a recursive DNS in the gateway
And that is completely fine
Ah that's it. Seems like I mixed up between DNS server types
Too bad Pi-Hole/dnsmasq can't be recursive. I installed bind to test:
Thank you @Nyr!
it would be create an ephmeral domain that nothing will have a cache and check who asked that domain on authoritive DNS server side.
Is that a good or bad thing?
Isn't that what they do with unbound?
What is the goal, though, to get around geo-location detection?
What are you referring to?
Yes.
Nice.. Didn't know about unbound. Learn new thing everyday on LET. I did the same thing with bind, though.
I'm referring to what @omelas said. Anyway the doc that @TimboJones referred earlier make everything clear
Run openvpn and pi hole on same server.
Here is a tutorial I wrote for my own use with debian or ubuntu based servers:
https://somik.org/ubuntu-18-04-install-pi-hole-with-pivpn/
We need to add this on the openvpn config for client in Windows:
Before adding that, my ip still leak with my ISP, such Telkom, and after adding that on client config, it's changed to the vps dns.
For Linux client, we had no problem/dns leak
Maybe i want my dns leaking.
I always using @Nyr script and never have any problem with that
oh, good then
The funny thing is sometimes it leaks and other times it doesn't. This is because Windows does not have a systemwide resolv.conf. Each network interface can have its own DNS. svchost.exe can and will send out DNS queries without respecting the routing table and the default gateway of the VPN tunnel, causing the leak.