Skip to content
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 scans broken for clients using DNS Encryption #1353

Open
anti4r opened this issue Oct 12, 2018 · 1 comment
Open

Nmap scans broken for clients using DNS Encryption #1353

anti4r opened this issue Oct 12, 2018 · 1 comment

Comments

@anti4r
Copy link

anti4r commented Oct 12, 2018

I use Stubby the DNS stub resolver to encrypt my DNS requests. When performing an NMAP scan of any kind, the scan fails with NSOCK ERROR [0.0570s] nsock_make_socket(): Socket trouble: Address family not supported by protocol nmap: nsock_core.c:1258: nsock_pool_add_event: Assertion nse->iod->sd >= 0' failed. [1] 870 abort (core dumped) nmap 127.0.0.1 for all targets and all versions of Nmap.

Problem confirmed by disabling stubby resolver and using default DNS servers.

@dmiller-nmap
Copy link

Thanks for the bug report! I'll look into this, but for now you can use either of these workarounds:

  1. Use the --dns-servers option to specify standard DNS servers to use with Nmap's parallel resolver. Ordinary UDP DNS queries will be sent to these servers, which is the fastest option for large numbers of targets.
  2. Use the --system-dns option to resolve addresses one at a time using gethostbyname, which should work fine with Stubby. Your queries ought to be sent via DNS-over-TLS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants