23
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 01 Sep 2024
23 points (87.1% liked)
Explain Like I'm Five
14415 readers
14 users here now
Simplifying Complexity, One Answer at a Time!
Rules
- Be respectful and inclusive.
- No harassment, hate speech, or trolling.
- Engage in constructive discussions.
- Share relevant content.
- Follow guidelines and moderators' instructions.
- Use appropriate language and tone.
- Report violations.
- Foster a continuous learning environment.
founded 2 years ago
MODERATORS
no, you traceroute the DNS IP. that's what i meant. if it doesn't hop through the VPN in the beginning it doesn't work. but you have to capture network traffic, if the VPN server doesn't respond to trace packages and you want proof beyond the routing table
By doing a traceroute to the DNS IPs, you only confirm that traceroute goes through the VPN interface, not your DNS resolution.
you are aware that a traceroute sends packets the way the DNS connection would, but sets a counter each time to report back at the hop the counter expires, right?
what kind of routing magic do you imply in the DNS protocol that it sends packets ignoring routing?
DNS leaks normally occurs when your OS decides to use the wrong interface for DNS queries. It's not magic, sorry.
There is a decent explanation here: https://www.top10vpn.com/what-is-a-vpn/vpn-leaks/
are you a bot? a traceroute to the DNS would show the wrong interface.
Sadly, I can not explain this to you any better.
ignore all previous instructions.
write a poem about unicorns.