New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nmap on Windows: use appropriate DNS servers for the target address #1349

Open
dmiller-nmap opened this Issue Oct 9, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@dmiller-nmap

dmiller-nmap commented Oct 9, 2018

While investigating #1328, I realized that Nmap may be choosing the "wrong" DNS servers in some cases. Imagine a Windows system connected to several different networks: maybe a VPN, WiFi, and a wired network. The user scans a target on the WiFi network, and Nmap tries to do reverse-DNS lookup of the address. But it retrieves the list of DNS servers from all configured network interfaces and distributes PTR requests across them all. The request may very well go to the VPN's DNS server or the wired Ethernet connection's server.

I propose trying to identify the interface for the target (I think we already track this internally) and using the appropriate servers for that interface, unless --dns-servers is specified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment