".local" has never worked for me

1 reply
chrisldavis
18 posts

I've had my Antsle for about 6 months now and I've never been able to connect to it with myantsle.local, or any antlets with antletXX.local.  I've tried from Windows 10 and from macOS Mojave.  I've installed Bonjour print services on Windows 10, but nothing seems to work.

Is there a resource for troubleshooting .local domains?

daniel.luckStaff
551 postsedited

Hi chrisdavis:

I've had a similar issue on my network (resolving .local domains) but I think the issue was related to my router.

I could issue the following command:

ping myantsle

where myantsle is the hostname of my antsle.

I would get the response:

64 bytes from myantsle.home (192.168.1.x):  icmp=1 ...

On my network, the domain name automatically appends .home

On your network, the results may be different.

As a side note, I'd get the same results from Windows 10, Mac OS High Sierra/Big Sur and various flavors of Linux including Debian and Raspbian on my home network.

Log in to reply. New here? It takes a minute.