Weird problem with avahi-daemon

Is this a new report?

Yes

System Info

Void 6.18.52_1 x86_64 GenuineIntel uptodate rrrrmFFFF

Package(s) Affected

avahi-0.8_2

Does a report exist for this bug with the project's home (upstream) and/or another distro?

No response

Expected behaviour

I should be able to resolve clients with just the hostname, it doesn't.

Actual behaviour

It goes in some sort of a strartup/crash loop when the system boots up. You restart the service and it seems as though it's working properly, but it still doesn't resolve hostnames. Tried it on 3 different rigs, it's the exact same behavior - boot into the loop, restart the service, seems like it's working fine, but it's not.

user@HOST ~> sudo sv status avahi-daemon
run: avahi-daemon: (pid 710) 0s
user@HOST ~> sudo sv status avahi-daemon
run: avahi-daemon: (pid 710) 0s
user@HOST ~> sudo sv status avahi-daemon
run: avahi-daemon: (pid 710) 0s
user@HOST ~> sudo sv restart avahi-daemon
ok: run: avahi-daemon: (pid 710) 0s
user@HOST ~> sudo sv status avahi-daemon
run: avahi-daemon: (pid 1723) 2s
user@HOST ~> sudo sv status avahi-daemon
run: avahi-daemon: (pid 1723) 4s
user@HOST ~> sudo sv status avahi-daemon
run: avahi-daemon: (pid 1723) 4s
user@HOST ~> avahi-resolve -4 -n KNOWN-HOST.local
Failed to resolve host name 'KNOWN-HOST.local': Timeout reached
user@HOST ~> avahi-resolve -4 -n $hostname.local
HOST.local	127.0.0.1

Steps to reproduce

1. Power on the rig.
2. Check the avahi-daemon, it should show 0s running even after a while.
3. Restart the service.
4. Now it seems like it's properly up, the uptime counter starts working.
5. Try and browse/resolve network hosts through hostname only, it doesn't work.

The report centers on avahi-daemon under runit: first reproduce the boot status with sv status avahi-daemon, then compare it with sv restart avahi-daemon and test avahi-resolve -4 -n .... Done means identifying why the service loops at boot and restoring hostname resolution after startup; the issue does not name a package file or test.