I can’t resolve (ping, ssh) any computer on my network from a newly installed minimal Gnome Desktop F39 on a laptop; since it’s minimal, it’s possible something’s missing from the installation.

trying from the laptop gives:

$ ping server.local
ping: server.local: Temporary failure in name resolution

pinging .box static DNS entries as well as IP addresses works. all other computers can resolve each other and the new laptop (1 debian, 1 fedora, 1 macOS), some have static, some dynamic IPs. they all get the DNS IP of my pi-hole, which resolves everything fine. resolve.conf and all other relevant files are stock. avahi and systemd-resolve are running and report no issues. same behaviour with WiFi and LAN.

I could switch to static IPs and assign e.g. .box suffixes all around via local DNS but I don’t want to do that, this setup is/was working on every other PC.

any ideas what I’m missing?

edit: just booted off of a live USB with F39, resolves server.local just fine. so I’m missing something in my installation, right?

edit II: installed it (minimal) on another laptop, same deal - no .local resolution.

  • setVeryLoud(true);@lemmy.ca
    1·
    11 months ago

    Thanks, I’ll have to try this.

    I have a home server running Fedora Server, and it doesn’t broadcast itself on .local all the time, it does it for a while after booting and then stops like a day later, or doesn’t until I poke the avahi and mdns services on the server. It’s extremely random. This is using clients on multiple OSes as well.

    • dingdongitsabear@lemmy.mlOP
      1·
      11 months ago

      I’m pretty sure that’s a separate issue. I’ve installed this laptop from the alternative, minimal install and thus I’m missing standard libs and tools on purpose. the idea is adding them as needed and not having bloat I don’t need.

      what you’re describing is different and I’ve experienced this behavior in the past on my desktop, I vividly remember trying to track the problem down - all other devices on the LAN announce and resolve .local just fine, only this fucker has these random spells.

      as to the solution, it kinda went away on its own, works without issues for the past x months or so. I can’t determine if it’s something that resolved itself on its own with upgrades or it’s something I’ve fixed, as it’s been upgraded in place from F35 onward and tinkered with frequently. but if I can look some configs up for you, let me know.