Forward DNS resolution failures after new parallel resolution change

[sfred92]

Hello to everyone,

DNS resolution is not working with Nmap 7.97 on Windows 11, except if I use the option "--system-dns":

---

Starting Nmap 7.97 ( https://nmap.org ) at 2025-05-20 14:45 +0200
Failed to resolve "www.lefigaro.fr".
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 4.82 seconds

---

Nping works fine:

---

Starting Nping 0.7.97 ( https://nmap.org/nping ) at 2025-05-20 14:46 Paris, Madrid (heure dÆÚtÚ)
SENT (0.8130s) ICMP [10.1.201.248 > 96.17.193.31 Echo request (type=8/code=0) id=5861 seq=1] IP [ttl=64 id=46936 iplen=28 ]
RCVD (0.8290s) ICMP [96.17.193.31 > 10.1.201.248 Echo reply (type=0/code=0) id=5861 seq=1] IP [ttl=52 id=59219 iplen=28 ]

---

Bug can be reproduced at each execution using FQDN.

OS: WIndows 11 Professional 23H2

---

C:>nmap --version
Nmap version 7.97 ( https://nmap.org )
Platform: i686-pc-windows-windows
Compiled with: nmap-liblua-5.4.7 openssl-3.0.16 nmap-libssh2-1.11.1 nmap-libz-1.3.1 nmap-libpcre2-10.45 Npcap-1.82 nmap-libdnet-1.18.0 ipv6
Compiled without:
Available nsock engines: iocp poll select

---

---

Starting Nmap 7.97 ( https://nmap.org ) at 2025-05-20 14:49 +0200
INTERFACES
DEV (SHORT) IP/MASK TYPE UP MTU MAC
eth0 (eth0) fe80::7648:b446:f7a2:7a62/64 ethernet down 1500 C4:C6:E6:9B:DA:38
eth0 (eth0) 169.254.160.204/16 ethernet down 1500 C4:C6:E6:9B:DA:38
eth1 (eth1) fe80::6d2c:bccc:27f9:4167/64 ethernet down 1500 40:86:CB:C9:0F:44
eth1 (eth1) 169.254.43.3/16 ethernet down 1500 40:86:CB:C9:0F:44
unk0 (unk0) fe80::d008:3ef6:53e5:5b13/64 other down 65535
unk0 (unk0) 169.254.89.88/16 other down 65535
unk1 (unk1) fe80::8e00:d71a:9c4e:aa6f/64 other down 1500
unk1 (unk1) 169.254.97.129/16 other down 1500
unk2 (unk2) fe80::80c5:a24:3e5:fe42/64 other down 1500
unk2 (unk2) 169.254.56.15/16 other down 1500
eth2 (eth2) fe80::3ca4:908a:3356:de80/64 ethernet down 1500 D0:65:78:6A:E1:82
eth2 (eth2) 169.254.18.127/16 ethernet down 1500 D0:65:78:6A:E1:82
eth3 (eth3) fe80::8f19:120b:92b9:615b/64 ethernet down 1500 D2:65:78:6A:E1:81
eth3 (eth3) 169.254.119.112/16 ethernet down 1500 D2:65:78:6A:E1:81
unk3 (unk3) fe80::18ca:da07:5d90:d5a6/64 other down 1500
unk3 (unk3) 169.254.23.86/16 other down 1500
eth4 (eth4) fe80::a8ce:8525:e075:d0bc/64 ethernet up 1500 00:50:56:C0:00:01
eth4 (eth4) 192.168.56.1/24 ethernet up 1500 00:50:56:C0:00:01
eth5 (eth5) fe80::abe1:47e9:4264:bb6/64 ethernet up 1500 00:50:56:C0:00:08
eth5 (eth5) 192.168.119.1/24 ethernet up 1500 00:50:56:C0:00:08
eth6 (eth6) fe80::ce93:c501:fada:6e00/64 ethernet up 1500 D0:65:78:6A:E1:81
eth6 (eth6) 10.1.201.248/24 ethernet up 1500 D0:65:78:6A:E1:81
eth7 (eth7) fe80::2e40:1ba0:f506:7d6/64 ethernet down 1500 D0:65:78:6A:E1:85
eth7 (eth7) 169.254.41.233/16 ethernet down 1500 D0:65:78:6A:E1:85
lo0 (lo0) ::1/128 loopback up -1
lo0 (lo0) 127.0.0.1/8 loopback up -1

DEV WINDEVICE
eth0 \Device\NPF_{65B54563-E14D-4445-B864-AAF85FDFA7F2}
eth0 \Device\NPF_{65B54563-E14D-4445-B864-AAF85FDFA7F2}
eth1 \Device\NPF_{659DB695-9E56-412A-9AFC-1154DAC8F42D}
eth1 \Device\NPF_{659DB695-9E56-412A-9AFC-1154DAC8F42D}
unk0 \Device\NPF_{39514B7B-F0DF-4A82-89D8-C66CFDFDF32E}
unk0 \Device\NPF_{39514B7B-F0DF-4A82-89D8-C66CFDFDF32E}
unk1 \Device\NPF_{02CD7C5C-D3CD-4E13-8871-3F7676D38CA1}
unk1 \Device\NPF_{02CD7C5C-D3CD-4E13-8871-3F7676D38CA1}
unk2 \Device\NPF_{936B38AC-C3F7-4827-AE71-3FCA54727C15}
unk2 \Device\NPF_{936B38AC-C3F7-4827-AE71-3FCA54727C15}
eth2 \Device\NPF_{B22EA5F4-1E47-46A3-9815-7B0754F746C7}
eth2 \Device\NPF_{B22EA5F4-1E47-46A3-9815-7B0754F746C7}
eth3 \Device\NPF_{F2EF4FEF-C7E2-4CE7-BB9D-BB1F5EB4558C}
eth3 \Device\NPF_{F2EF4FEF-C7E2-4CE7-BB9D-BB1F5EB4558C}
unk3 \Device\NPF_{2E53CBF3-4FB1-4E66-9AFA-7F3452F8F5A1}
unk3 \Device\NPF_{2E53CBF3-4FB1-4E66-9AFA-7F3452F8F5A1}
eth4 \Device\NPF_{9BBF2007-7067-420E-A500-B600195F1791}
eth4 \Device\NPF_{9BBF2007-7067-420E-A500-B600195F1791}
eth5 \Device\NPF_{A98461AF-CAEA-4739-BA04-9E262B1EB1D6}
eth5 \Device\NPF_{A98461AF-CAEA-4739-BA04-9E262B1EB1D6}
eth6 \Device\NPF_{15C1CFE8-FE0C-41D0-9249-ADC32D2FA0FB}
eth6 \Device\NPF_{15C1CFE8-FE0C-41D0-9249-ADC32D2FA0FB}
eth7 \Device\NPF_{8F669C44-6F11-4BE5-AC37-E3F580BAC10E}
eth7 \Device\NPF_{8F669C44-6F11-4BE5-AC37-E3F580BAC10E}
lo0 \Device\NPF_Loopback
lo0 \Device\NPF_Loopback
\Device\NPF_{DC776BC6-54CD-4AA8-AC4D-28CF6AA74F1A}
\Device\NPF_{38FCE250-0EB2-47A3-A6AB-5D14FDC082DE}
\Device\NPF_{0FA7D2F3-0582-4443-B581-C937BC60111F}

ROUTES
DST/MASK DEV METRIC GATEWAY
255.255.255.255/32 eth0 261
255.255.255.255/32 eth1 261
255.255.255.255/32 unk0 261
255.255.255.255/32 eth3 281
255.255.255.255/32 eth2 281
255.255.255.255/32 unk3 281
255.255.255.255/32 unk1 281
255.255.255.255/32 unk2 281
255.255.255.255/32 eth6 291
10.1.201.255/32 eth6 291
192.168.56.1/32 eth4 291
10.1.201.248/32 eth6 291
192.168.119.255/32 eth5 291
192.168.119.1/32 eth5 291
192.168.56.255/32 eth4 291
255.255.255.255/32 eth5 291
255.255.255.255/32 eth4 291
255.255.255.255/32 eth7 321
127.0.0.1/32 lo0 331
255.255.255.255/32 lo0 331
127.255.255.255/32 lo0 331
10.1.201.0/24 eth6 291
192.168.119.0/24 eth5 291
192.168.56.0/24 eth4 291
127.0.0.0/8 lo0 331
224.0.0.0/4 eth1 261
224.0.0.0/4 eth0 261
224.0.0.0/4 unk0 261
224.0.0.0/4 unk1 281
224.0.0.0/4 eth2 281
224.0.0.0/4 unk3 281
224.0.0.0/4 unk2 281
224.0.0.0/4 eth3 281
224.0.0.0/4 eth5 291
224.0.0.0/4 eth4 291
224.0.0.0/4 eth6 291
224.0.0.0/4 eth7 321
224.0.0.0/4 lo0 331
0.0.0.0/0 eth6 35 10.1.201.1
fe80::7648:b446:f7a2:7a62/128 eth0 261
fe80::d008:3ef6:53e5:5b13/128 unk0 261
fe80::6d2c:bccc:27f9:4167/128 eth1 261
fe80::8e00:d71a:9c4e:aa6f/128 unk1 281
fe80::18ca:da07:5d90:d5a6/128 unk3 281
fe80::8f19:120b:92b9:615b/128 eth3 281
fe80::3ca4:908a:3356:de80/128 eth2 281
fe80::80c5:a24:3e5:fe42/128 unk2 281
fe80::a8ce:8525:e075:d0bc/128 eth4 291
fe80::abe1:47e9:4264:bb6/128 eth5 291
fe80::ce93:c501:fada:6e00/128 eth6 291
fe80::2e40:1ba0:f506:7d6/128 eth7 321
::1/128 lo0 331
fe80::/64 eth0 261
fe80::/64 unk0 261
fe80::/64 eth1 261
fe80::/64 eth3 281
fe80::/64 eth2 281
fe80::/64 unk2 281
fe80::/64 unk3 281
fe80::/64 unk1 281
fe80::/64 eth6 291
fe80::/64 eth4 291
fe80::/64 eth5 291
fe80::/64 eth7 321
ff00::/8 unk0 261
ff00::/8 eth1 261
ff00::/8 eth0 261
ff00::/8 eth3 281
ff00::/8 unk2 281
ff00::/8 unk1 281
ff00::/8 eth2 281
ff00::/8 unk3 281
ff00::/8 eth5 291
ff00::/8 eth6 291
ff00::/8 eth4 291
ff00::/8 eth7 321
ff00::/8 lo0 331

---

I had never met this bug before, including with previous Nmap 7.95.

Thank you
Fred

[dmiller-nmap]

Thanks for reporting this! We need a little more info for us to see why Nmap might be having trouble. Please provide output for the following commands:

1. nmap -n -sL -d2 www.lefigaro.fr
2. nslookup www.lefigaro.fr
3. ipconfig /all

[sfred92]

Hi,
Here are the outputs:

C:\>nmap -n -sL -d2 www.lefigaro.fr
npcap service is already running.
Packet.dll present, library version 1.82
wpcap.dll present, library version: Npcap version 1.82, based on libpcap version 1.10.5
Starting Nmap 7.97 ( https://nmap.org ) at 2025-05-21 09:19 +0200
Fetchfile found C:\Program Files (x86)\Nmap/nmap.xsl
The max # of sockets we are using is: 0
--------------- Timing report ---------------
  hostgroups: min 1, max 100000
  rtt-timeouts: init 1000, min 100, max 10000
  max-scan-delay: TCP 1000, UDP 1000, SCTP 1000
  parallelism: min 0, max 0
  max-retries: 10, host-timeout: 0
  min-rate: 0, max-rate: 0
---------------------------------------------
mass_dns: Using DNS server 192.168.101.32
mass_dns: Using DNS server 192.168.101.46
mass_dns: Using DNS server 192.168.101.32
mass_dns: Using DNS server 192.168.101.46
Interface {17a62cdf-839b-11ee-9098-806e6f6e6963} is not known; ignoring its nameservers.
Interface {1a20995f-a6f1-478a-a4ee-9badd6627ca8} is not known; ignoring its nameservers.
mass_dns: Using DNS server 172.20.2.39
mass_dns: Using DNS server 172.20.2.10
Interface {36168c7c-9336-47cb-bdf4-8719b10bb661} is not known; ignoring its nameservers.
Interface {4f366d9c-1904-4887-a7ea-54e96e7d53b2} is not known; ignoring its nameservers.
Interface {54d025f6-5607-42cf-a2be-00135bd4648e} is not known; ignoring its nameservers.
mass_dns: Using DNS server 192.168.74.254
Interface {69d58e28-c96c-4485-b40c-78e25d30f6b0} is not known; ignoring its nameservers.
Interface {886f7157-1024-4122-8087-d73db04351bb} is not known; ignoring its nameservers.
Interface {adf2ac4e-8b2d-4c02-9571-96aa95c034df} is not known; ignoring its nameservers.
Interface {b2111cad-c257-4627-9311-5c435d8b97f4} is not known; ignoring its nameservers.
Interface {bf62e120-b98a-45e5-8209-19940b9b0946} is not known; ignoring its nameservers.
Interface {d3f96b3b-bda5-4d98-b908-ce8cf27666b1} is not known; ignoring its nameservers.
Interface {e0b1573b-d383-4528-8098-b8732b08ba77} is not known; ignoring its nameservers.
Interface {e4b4fa2b-a51d-4d11-9b0c-624887365a10} is not known; ignoring its nameservers.
Interface {ea7a21f4-cb9c-4a89-b1ca-72ceffb0a7cc} is not known; ignoring its nameservers.
NSOCK INFO [0.2000s] nsock_iod_new2(): nsock_iod_new (IOD #1)
NSOCK INFO [0.2010s] nsock_connect_udp(): UDP connection requested to 192.168.74.254:53 (IOD #1) EID 8
NSOCK INFO [0.2010s] nsock_read(): Read request from IOD #1 [192.168.74.254:53] (timeout: -1ms) EID 18
NSOCK INFO [0.2010s] nsock_iod_new2(): nsock_iod_new (IOD #2)
NSOCK INFO [0.2010s] nsock_connect_udp(): UDP connection requested to 172.20.2.10:53 (IOD #2) EID 24
NSOCK INFO [0.2020s] nsock_read(): Read request from IOD #2 [172.20.2.10:53] (timeout: -1ms) EID 34
NSOCK INFO [0.2020s] nsock_iod_new2(): nsock_iod_new (IOD #3)
NSOCK INFO [0.2020s] nsock_connect_udp(): UDP connection requested to 172.20.2.39:53 (IOD #3) EID 40
NSOCK INFO [0.2020s] nsock_read(): Read request from IOD #3 [172.20.2.39:53] (timeout: -1ms) EID 50
NSOCK INFO [0.2020s] nsock_iod_new2(): nsock_iod_new (IOD #4)
NSOCK INFO [0.2020s] nsock_connect_udp(): UDP connection requested to 192.168.101.46:53 (IOD #4) EID 56
NSOCK INFO [0.2020s] nsock_read(): Read request from IOD #4 [192.168.101.46:53] (timeout: -1ms) EID 66
NSOCK INFO [0.2020s] nsock_iod_new2(): nsock_iod_new (IOD #5)
NSOCK INFO [0.2020s] nsock_connect_udp(): UDP connection requested to 192.168.101.32:53 (IOD #5) EID 72
NSOCK INFO [0.2020s] nsock_read(): Read request from IOD #5 [192.168.101.32:53] (timeout: -1ms) EID 82
NSOCK INFO [0.2020s] nsock_iod_new2(): nsock_iod_new (IOD #6)
NSOCK INFO [0.2020s] nsock_connect_udp(): UDP connection requested to 192.168.101.46:53 (IOD #6) EID 88
NSOCK INFO [0.2020s] nsock_read(): Read request from IOD #6 [192.168.101.46:53] (timeout: -1ms) EID 98
NSOCK INFO [0.2020s] nsock_iod_new2(): nsock_iod_new (IOD #7)
NSOCK INFO [0.2020s] nsock_connect_udp(): UDP connection requested to 192.168.101.32:53 (IOD #7) EID 104
NSOCK INFO [0.2030s] nsock_read(): Read request from IOD #7 [192.168.101.32:53] (timeout: -1ms) EID 114
Initiating Parallel DNS resolution of 1 host. at 09:19
NSOCK INFO [0.2030s] nsock_write(): Write request for 33 bytes to IOD #1 EID 123 [192.168.74.254:53]
NSOCK INFO [0.2030s] nsock_write(): Write request for 33 bytes to IOD #2 EID 131 [172.20.2.10:53]
NSOCK INFO [0.2030s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 8 [192.168.74.254:53]
NSOCK INFO [0.2030s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 123 [192.168.74.254:53]
NSOCK INFO [0.2030s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 24 [172.20.2.10:53]
NSOCK INFO [0.2030s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 131 [172.20.2.10:53]
NSOCK INFO [0.2030s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 40 [172.20.2.39:53]
NSOCK INFO [0.2030s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 56 [192.168.101.46:53]
NSOCK INFO [0.2030s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 72 [192.168.101.32:53]
NSOCK INFO [0.2030s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 88 [192.168.101.46:53]
NSOCK INFO [0.2030s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 104 [192.168.101.32:53]
NSOCK INFO [0.2090s] nsock_trace_handler_callback(): Callback: READ ERROR [La connexion a ÚtÚ interrompue en raison dÆun maintien dÆactivitÚ ayant dÚtectÚ un Úchec lorsque lÆopÚration Útait en cours.  (10052)] for EID 18 [192.168.74.254:53]
NSOCK INFO [0.2090s] nsock_read(): Read request from IOD #1 [192.168.74.254:53] (timeout: -1ms) EID 138
mass_dns: warning: got a READ:ERROR in read_evt_handler()
NSOCK INFO [0.7180s] nsock_write(): Write request for 33 bytes to IOD #1 EID 147 [192.168.74.254:53]
NSOCK INFO [0.7180s] nsock_write(): Write request for 33 bytes to IOD #2 EID 155 [172.20.2.10:53]
NSOCK INFO [0.7190s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 147 [192.168.74.254:53]
NSOCK INFO [0.7190s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 155 [172.20.2.10:53]
NSOCK INFO [0.7240s] nsock_trace_handler_callback(): Callback: READ ERROR [La connexion a ÚtÚ interrompue en raison dÆun maintien dÆactivitÚ ayant dÚtectÚ un Úchec lorsque lÆopÚration Útait en cours.  (10052)] for EID 138 [192.168.74.254:53]
NSOCK INFO [0.7240s] nsock_read(): Read request from IOD #1 [192.168.74.254:53] (timeout: -1ms) EID 162
mass_dns: warning: got a READ:ERROR in read_evt_handler()
NSOCK INFO [1.7230s] nsock_write(): Write request for 33 bytes to IOD #2 EID 171 [172.20.2.10:53]
NSOCK INFO [1.7240s] nsock_write(): Write request for 33 bytes to IOD #3 EID 179 [172.20.2.39:53]
NSOCK INFO [1.7240s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 171 [172.20.2.10:53]
NSOCK INFO [1.7240s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 179 [172.20.2.39:53]
NSOCK INFO [2.2250s] nsock_write(): Write request for 33 bytes to IOD #2 EID 187 [172.20.2.10:53]
NSOCK INFO [2.2250s] nsock_write(): Write request for 33 bytes to IOD #3 EID 195 [172.20.2.39:53]
NSOCK INFO [2.2250s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 187 [172.20.2.10:53]
NSOCK INFO [2.2250s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 195 [172.20.2.39:53]
NSOCK INFO [3.2290s] nsock_write(): Write request for 33 bytes to IOD #3 EID 203 [172.20.2.39:53]
NSOCK INFO [3.2290s] nsock_write(): Write request for 33 bytes to IOD #4 EID 211 [192.168.101.46:53]
NSOCK INFO [3.2300s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 203 [172.20.2.39:53]
NSOCK INFO [3.2300s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 211 [192.168.101.46:53]
NSOCK INFO [3.2370s] nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 66 [192.168.101.46:53] (108 bytes)
NSOCK INFO [3.2370s] nsock_read(): Read request from IOD #4 [192.168.101.46:53] (timeout: -1ms) EID 218
NSOCK INFO [3.7310s] nsock_write(): Write request for 33 bytes to IOD #3 EID 227 [172.20.2.39:53]
NSOCK INFO [3.7310s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 227 [172.20.2.39:53]
mass_dns: 4.72s 0/2 [#: 7, OK: 0, NX: 0, DR: 0, SF: 0, TR: 11]
Completed Parallel DNS resolution of 1 host. at 09:19, 4.53s elapsed
NSOCK INFO [4.7360s] nsock_iod_delete(): nsock_iod_delete (IOD #1)
NSOCK INFO [4.7360s] nevent_delete(): nevent_delete on event #162 (type READ)
NSOCK INFO [4.7360s] nsock_iod_delete(): nsock_iod_delete (IOD #2)
NSOCK INFO [4.7360s] nevent_delete(): nevent_delete on event #34 (type READ)
NSOCK INFO [4.7360s] nsock_iod_delete(): nsock_iod_delete (IOD #3)
NSOCK INFO [4.7360s] nevent_delete(): nevent_delete on event #50 (type READ)
NSOCK INFO [4.7360s] nsock_iod_delete(): nsock_iod_delete (IOD #4)
NSOCK INFO [4.7360s] nevent_delete(): nevent_delete on event #218 (type READ)
NSOCK INFO [4.7360s] nsock_iod_delete(): nsock_iod_delete (IOD #5)
NSOCK INFO [4.7360s] nevent_delete(): nevent_delete on event #82 (type READ)
NSOCK INFO [4.7360s] nsock_iod_delete(): nsock_iod_delete (IOD #6)
NSOCK INFO [4.7360s] nevent_delete(): nevent_delete on event #98 (type READ)
NSOCK INFO [4.7360s] nsock_iod_delete(): nsock_iod_delete (IOD #7)
NSOCK INFO [4.7360s] nevent_delete(): nevent_delete on event #114 (type READ)
DNS resolution of 2 IPs took 4.72s. Mode: Async [#: 7, OK: 0, NX: 0, DR: 1, SF: 0, TR: 11, CN: 0]
Failed to resolve "www.lefigaro.fr".
No data files read.
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 4.74 seconds

C:\>nslookup www.lefigaro.fr
Serveur :   controller.intra.lan
Address:  192.168.101.32

Réponse ne faisant pas autorité :
Nom :    e26587.b.akamaiedge.net
Addresses:  96.17.193.34
          96.17.193.21
          96.17.193.19
          96.17.193.29
          96.17.193.30
          96.17.193.17
          96.17.193.32
          96.17.193.25
          96.17.193.22
Aliases:  www.lefigaro.fr
          www.lefigaro.fr.edgekey.net

C:\>ipconfig /all

Configuration IP de Windows

   Nom de l’hôte . . . . . . . . . . : LAN000505
   Suffixe DNS principal . . . . . . : lan.corp
   Type de noeud. . . . . . . . . .  : Hybride
   Routage IP activé . . . . . . . . : Non
   Proxy WINS activé . . . . . . . . : Non
   Liste de recherche du suffixe DNS.: lan.corp

Carte Ethernet Ethernet :

   Statut du média. . . . . . . . . . . . : Média déconnecté
   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Intel(R) Ethernet Connection (18) I219-V
   Adresse physique . . . . . . . . . . . : C4-C6-E6-9B-DA-38
   DHCP activé. . . . . . . . . . . . . . : Oui
   Configuration automatique activée. . . : Oui

Carte Ethernet Ethernet 4 :

   Statut du média. . . . . . . . . . . . : Média déconnecté
   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Realtek USB GbE Family Controller
   Adresse physique . . . . . . . . . . . : 40-86-CB-C9-0F-44
   DHCP activé. . . . . . . . . . . . . . : Oui
   Configuration automatique activée. . . : Oui

Carte inconnue OpenVPN Wintun :

   Statut du média. . . . . . . . . . . . : Média déconnecté
   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Wintun Userspace Tunnel
   Adresse physique . . . . . . . . . . . :
   DHCP activé. . . . . . . . . . . . . . : Non
   Configuration automatique activée. . . : Oui

Carte inconnue OpenVPN TAP-Windows6 :

   Statut du média. . . . . . . . . . . . : Média déconnecté
   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : TAP-Windows Adapter V9
   Adresse physique . . . . . . . . . . . : 00-FF-02-CD-7C-5C
   DHCP activé. . . . . . . . . . . . . . : Oui
   Configuration automatique activée. . . : Oui

Carte inconnue OpenVPN Data Channel Offload :

   Statut du média. . . . . . . . . . . . : Média déconnecté
   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : OpenVPN Data Channel Offload
   Adresse physique . . . . . . . . . . . :
   DHCP activé. . . . . . . . . . . . . . : Oui
   Configuration automatique activée. . . : Oui

Carte réseau sans fil Connexion au réseau local* 1 :

   Statut du média. . . . . . . . . . . . : Média déconnecté
   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Adresse physique . . . . . . . . . . . : D0-65-78-6A-E1-82
   DHCP activé. . . . . . . . . . . . . . : Oui
   Configuration automatique activée. . . : Oui

Carte réseau sans fil Connexion au réseau local* 2 :

   Statut du média. . . . . . . . . . . . : Média déconnecté
   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
   Adresse physique . . . . . . . . . . . : D2-65-78-6A-E1-81
   DHCP activé. . . . . . . . . . . . . . : Non
   Configuration automatique activée. . . : Oui

Carte haut débit mobile Cellulaire :

   Statut du média. . . . . . . . . . . . : Média déconnecté
   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Quectel RM520N-GL
   Adresse physique . . . . . . . . . . . : 00-A0-C6-00-00-01
   DHCP activé. . . . . . . . . . . . . . : Non
   Configuration automatique activée. . . : Oui

Carte Ethernet VMware Network Adapter VMnet1 :

   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
   Adresse physique . . . . . . . . . . . : 00-50-56-C0-00-01
   DHCP activé. . . . . . . . . . . . . . : Non
   Configuration automatique activée. . . : Oui
   Adresse IPv6 de liaison locale. . . . .: fe80::a8ce:8525:e075:d0bc%23(préféré)
   Adresse IPv4. . . . . . . . . . . . . .: 192.168.56.1(préféré)
   Masque de sous-réseau. . . . . . . . . : 255.255.255.0
   Passerelle par défaut. . . . . . . . . :
   IAID DHCPv6 . . . . . . . . . . . : 218124374
   DUID de client DHCPv6. . . . . . . . : 00-01-00-01-2E-3B-1E-94-C4-C6-E6-9B-DA-38
   NetBIOS sur TCPIP. . . . . . . . . . . : Désactivé

Carte Ethernet VMware Network Adapter VMnet8 :

   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
   Adresse physique . . . . . . . . . . . : 00-50-56-C0-00-08
   DHCP activé. . . . . . . . . . . . . . : Non
   Configuration automatique activée. . . : Oui
   Adresse IPv6 de liaison locale. . . . .: fe80::abe1:47e9:4264:bb6%24(préféré)
   Adresse IPv4. . . . . . . . . . . . . .: 192.168.119.1(préféré)
   Masque de sous-réseau. . . . . . . . . : 255.255.255.0
   Passerelle par défaut. . . . . . . . . :
   IAID DHCPv6 . . . . . . . . . . . : 620777558
   DUID de client DHCPv6. . . . . . . . : 00-01-00-01-2E-3B-1E-94-C4-C6-E6-9B-DA-38
   NetBIOS sur TCPIP. . . . . . . . . . . : Désactivé

Carte réseau sans fil Wi-Fi :

   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Intel(R) Wi-Fi 6E AX211 160MHz
   Adresse physique . . . . . . . . . . . : D0-65-78-6A-E1-81
   DHCP activé. . . . . . . . . . . . . . : Oui
   Configuration automatique activée. . . : Oui
   Adresse IPv6 de liaison locale. . . . .: fe80::ce93:c501:fada:6e00%5(préféré)
   Adresse IPv4. . . . . . . . . . . . . .: 10.1.201.248(préféré)
   Masque de sous-réseau. . . . . . . . . : 255.255.255.0
   Bail obtenu. . . . . . . . . . . . . . : mercredi 21 mai 2025 09:15:22
   Bail expirant. . . . . . . . . . . . . : jeudi 22 mai 2025 09:15:22
   Passerelle par défaut. . . . . . . . . : 10.1.201.1
   Serveur DHCP . . . . . . . . . . . . . : 10.1.201.1
   IAID DHCPv6 . . . . . . . . . . . : 97543544
   DUID de client DHCPv6. . . . . . . . : 00-01-00-01-2E-3B-1E-94-C4-C6-E6-9B-DA-38
   Serveurs DNS. . .  . . . . . . . . . . : 192.168.101.32
                                       192.168.101.46
   NetBIOS sur TCPIP. . . . . . . . . . . : Désactivé

Carte Ethernet Connexion réseau Bluetooth :

   Statut du média. . . . . . . . . . . . : Média déconnecté
   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Adresse physique . . . . . . . . . . . : D0-65-78-6A-E1-85
   DHCP activé. . . . . . . . . . . . . . : Oui
   Configuration automatique activée. . . : Oui

Thank you.

Have a good day.
Fred

[dmiller-nmap]

Thanks for the additional info. It looks like Nmap is retrieving some DNS server addresses that were configured on adapters that are not currently up. Because they were not reachable (due to being in a different private IP range than you are currently connected to), the requests timed out. For speed, we only try up to 3 servers per name before giving up, so we never even got as far as sending the request to the DNS servers on the active connection.

To resolve this issue, we will need to change our approach to finding DNS servers. We should not be reading them from the Registry, but should instead use GetAdaptersAddresses() to retrieve them. Additionally, we should allow the -e option to limit to only the servers for the specified adapter. Finally, we should be more clever about how we choose which servers to use: for forward lookups without -e, we should make sure we use at least 1 server from each adapter that is up; and for reverse lookups we should favor the servers that are configured on the source adapter we have chosen for that target.

You should be able to use --dns-servers 192.168.101.32,192.168.101.46 in your nmap command as a workaround until we can get a more permanent fix in place.

[sfred92]

Hi,

Thank you for your comment.

As you say, as a workaround up to this bug resolution, I can use "--dns -servers" option, but I also can use "--system-dns".

Have a nice day and long life to Nmap
Fred