What type of hardware are you using: Old laptop or computer What YunoHost version are you running: 12.1.17.1 (stable) How are you able to access your server: The webadmin Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: No
Describe your issue
Hello my clever YNH chums! The demand for YNH among my relatives is growing and I’m building another one for my neighbour now. With this one I have come across an issue that seems to be mentioned many times in this forum but never seems to get a clean resolution. It looks to me as if the issue is simple but I have no inkling about a decent fix. On this new build I have paced six local domains to host Immich, Cockpit, Nextcloud, Searxng, Vaultwarden and finally an empty main domain. When first built they all resolved OK and worked well. However, after a reboot YNH was unable to resolve any local DNS address. After digging in to the forum it looks like an issue with yunomdns. If I use the command “systemctl status yunomdns” I can only see the main.local domain listed. If I then “stop” yunomdns and then “start” yunomdns, followed by the “status” command they are all now listed. Many other seem to have had very similar issues (but with much more complicated support data), is this a bug? Any insight or guidance welcomed. I could add the commands to crontab but that feels like a sticking plaster rather than a solution. Advice welcomed.
Hmmmyeah I’ve seen similar issues outside yunohost with avahi-daemon (the predecessor to yunomdns) … Unfortunately to me the conclusion across the years is that mDNS a.k.a. the bonjour protocol is generally-speaking not reliable, partly because somehow you need to restart the mDNS server regularly to re-broadcast it (?), and because some clients like mobile browser don’t support it ? (And possibly regular computers too if they’re missing the corresponding library)
I wish somebody would argue for a different conclusion x_x
Interesting, and thanks for the feedback. It seems to be a common issue but no one has a strong answer. Wierdly I have my own YNH server on the same LAN with local domains and it has never had any problems. I feel there must be some diffrence between the new server I am building for my neighbour and my original one. They in effect perform differently on the same network but have the same software and apps installed. It feels as though we need an ‘out of the box’ new approach to what appears to be an old intermittent issue. Sadly it’s beyond my minimal Linux (and 40 year old Unix) knowledge.