.local Host Name Only Works Sometimes

Paul Naish

March 10, 2023 20:42

Apologies if this has been asked elsewhere in this forum but the search drops the "." in ".local".

I need to use a local host name because my deployment will be changing subnets over time. Sometimes wethCAM.local works with VNCviewer and other times it doesn't. It always works with the IP address

Here's what I see from Windows 10

$ ping wethCAM.local

Pinging wethCAM.local [192.168.1.141] with 32 bytes of data:
Reply from 192.168.1.141: bytes=32 time=1ms TTL=64
Reply from 192.168.1.141: bytes=32 time=1ms TTL=64
Reply from 192.168.1.141: bytes=32 time=1ms TTL=64
Reply from 192.168.1.141: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.141:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

Of course I don't expect to see it from a DNS lookup

$ nslookup wethCAM.local
Server: mynetwork
Address: 192.168.1.1

*** mynetwork can't find wethCAM.local: Non-existent domain

The error returned from VNCviewer is "Timed out waiting for a response from the computer'

Is there a configuration to enable ".local" support in VNC?

Thanks

.local Host Name Only Works Sometimes

Comments

Didn't find what you were looking for?