Explanation of mapdns options?

[ronandalton]

Hi, I was wondering what the mapdns config options do. I can't see any documentation for this in the readme. Does it do something like what as described in this issue: #197?

... some kind of "fake resolver" that maps A queries to addresses from "unused" range while tunneling part replaces those fake addresses to mapped hostnames back when sending command to socks server

Thanks!

[heiher]

Map DNS is a feature that intercepts local DNS requests, returning “fake” IPs or resolving the real IPs through the proxy server instead of using the system or ISP DNS. This prevents DNS leaks, protects privacy, and enables domain-based traffic routing.

[ronandalton]

Did you respond to my question with an AI generated answer?

returning “fake” IPs or resolving the real IPs

Which method does your application implement?

Also, would it make sense to close the linked issue as complete since this is implemented now?

Cheers

[ronandalton]

I found my answer here: https://hev.cc/posts/2025/tun2socks-mapped-dns/

Here's a Google-translated version:

Mapped DNS works as follows:

• When a client application initiates a domain name resolution request, the Mapped DNS module returns a "Fake IP" instead of the actual target server IP.
• These "Fake IPs" come from a predefined Fake IP address segment. These addresses do not have corresponding real servers on the Internet and are only used internally by the proxy.
• Subsequently, when the client tries to connect to this fake IP, HevSocks5Tunnel will restore this fake IP to the original domain name through the internal mapping table, and then forward it through the SOCKS5 proxy.
• In this way, the proxy program can know the original domain name, thereby realizing domain name-based diversion, blocking, DNS hijacking avoidance and other functions.

So yes it works as I thought.