I recently added a Raspberry Pi to my network, with the intention of using it as a basis for a printserver/fileserver in my home network. The Pi is running fine, so now I want to connect to it.
On my (Mac) laptop, the Pi was immediately accessible as raspberrypi.local, which was great.
On the family computer (running Tumbleweed), the Pi is only accessible through the IP address, but not through raspberrypi.local. I found several examples of this happening to other people using other distributions (for instance https://askubuntu.com/questions/1068131/ubuntu-18-04-local-domain-dns-lookup-not-working, https://unix.stackexchange.com/questions/457166/can-not-resolve-local-domains-internal-to-my-office-lan) but these didn’t help me resolve the issue - in part because the mdns services are different, or the suggested tools appear to be outdated.
What I know:
- It works on my laptop (and iPad), so it doesn’t appear to be an issue with either the Pi or the router.
- Connecting using the IP address works
- It doesn’t appear to be caused by the firewall (the problem persists if I disable the firewall)
- Faffing around with random suggestions to change things in /etc/systemd/resolved.conf and /etc/avahi/avahi-daemon.conf didn’t help (I reverted the changes back to the stock values)
So, I could use some help figuring out how to fix this. At the moment, I’m not sure where to look next and what to try next. Suggestions appreciated.
In the past, I just assigned a static IP to my fixed computer and added it to /etc/hosts. I could do that now too, but I would like something scalable that doesn’t require me to manually tweak /etc/hosts on every computer in the house - and I’d like to be able to troubleshoot and fix this if it comes up again in the future.