nslookup not working

[fishouttah20]

# nslookup microsoft.com
socket.c:2447: setsockopt(20, SO_TIMESTAMP) failed: Invalid argument
socket.c:1915: internal_send: 158.43.240.4#53: Invalid argument
socket.c:2447: setsockopt(21, SO_TIMESTAMP) failed: Invalid argument
socket.c:1915: internal_send: 158.43.128.72#53: Invalid argument
socket.c:2447: setsockopt(22, SO_TIMESTAMP) failed: Invalid argument
socket.c:1915: internal_send: 194.168.4.100#53: Invalid argument
socket.c:1915: internal_send: 158.43.240.4#53: Invalid argument
socket.c:1915: internal_send: 158.43.128.72#53: Invalid argument
socket.c:1915: internal_send: 194.168.4.100#53: Invalid argument
socket.c:1915: internal_send: 158.43.240.4#53: Invalid argument
socket.c:1915: internal_send: 158.43.128.72#53: Invalid argument
socket.c:1915: internal_send: 194.168.4.100#53: Invalid argument
;; connection timed out; no servers could be reached

[fishouttah20]

Looks like more than just nslookup affected by socket.c. #69

[christoh]

same with dig and host

[ion-storm]

Same with ping, hopefully these get fixed since I use these daily

[sunilmut]

We understand the frustration of not having networking tools enabled in the WSL and are looking to enable them gradually. The problem is the lack of the underlying socket implementation such as NETLINK, INET/SOCK_RAW/ICMP in WSL. We appreciate the feedback and please help us prioritize this by up voting enabling network interface enumeration in the User Voice page.

[russalex]

nslookup is working much better in current builds. As this is an old thread I will close out.