I have an existing stock Ubuntu server on my network. Let's say its hostname is "my-server". (The following should work with a stock Mac as well; not sure about Windows servers?)
If I open up a regular Command Prompt, I can do the following:
C:\Users\me>ping my-server.local
Pinging my-server [10.0.0.1] with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time=3ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Ping statistics for 10.10.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 1ms
But from Bash-on-Windows:
bash-on-windows$ ping my-server.local
ping: unknown host my-server.local
For comparison, from a real Ubuntu machine on the same network, I can do:
real-linux$ ping my-server.local
PING my-server.local (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.206 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.138 ms
64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.130 ms
(...)
Granted, ping wouldn't work even if it could resolve the name due to #18 , but other tools like curl or ssh would work if appropriate services were running on the server. I'm just trying to post a minimal reproducer.
I have an existing stock Ubuntu server on my network. Let's say its hostname is "my-server". (The following should work with a stock Mac as well; not sure about Windows servers?)
If I open up a regular Command Prompt, I can do the following:
But from Bash-on-Windows:
For comparison, from a real Ubuntu machine on the same network, I can do:
Granted,
pingwouldn't work even if it could resolve the name due to #18 , but other tools likecurlorsshwould work if appropriate services were running on the server. I'm just trying to post a minimal reproducer.