I've seen this discussed with no sure solution other than using a static IP address other than host.local and/or create entries in /etc/hosts.
On my two networks, host.local works 90% of time which is not good enough for reliable TCP/IP communications. I have one here at home and one at my cottage. They use different ISP's and routers.
I've found that rebooting a PI often gets the host.local working. In other cases, just waiting a couple of minutes seems to properly resolve it.
I tried to look in this forum but the search in ".local' drops the '.'. I found some information Googling but it got into network configurations I did not understand how to check/enable on RPO OS Bullseye.
I'm hoping others may have succeeded in improving the resolution rate.
Thanks
On my two networks, host.local works 90% of time which is not good enough for reliable TCP/IP communications. I have one here at home and one at my cottage. They use different ISP's and routers.
I've found that rebooting a PI often gets the host.local working. In other cases, just waiting a couple of minutes seems to properly resolve it.
I tried to look in this forum but the search in ".local' drops the '.'. I found some information Googling but it got into network configurations I did not understand how to check/enable on RPO OS Bullseye.
I'm hoping others may have succeeded in improving the resolution rate.
Thanks
Statistics: Posted by DS256 — Thu Aug 08, 2024 2:28 pm — Replies 2 — Views 28