[SOLVED] Pi/moOde non-responsive after inactivity - suggestions?

[the_bertrum]

You've got a working solution so this is just random information.

I have no DNS service running on my LAN so I resolve all my hosts by mDNS, e.g., with <bletch>.local names. There's more than a dozen hosts on the LAN, ranging from moOde players and Linux boxes, to my partner's Windows laptop and smart TV, etc.

I've noticed occasionally that I'll try, for example, to ping or ssh from one host to another only to  have the process time out with a "Could not resolve..." message. If I immediately try again, the connection completes. I haven't bothered to figure out why this happens. Apart from it, communication on my LAN is robust.

Of course using the IP address works without fail, assuming my router is healthy. In the good old days before DNS we Unix-ers had to exchange lengthy /etc/hosts files relating IP addresses to hostnames so we could find each other easily.

Regards,
Kent

Very much a similar situation to me, apart from once my Pixel 6 gets a could not resolve it won't come back again unless I force the Pixel to refresh its connection (either by restarting it, or by asking it to connect to the "bad" host with no network connection at all).  When it's gone it is really gone too, all browsers, ssh clients, whatever on the Pixel refuse to connect, although mDNS tools can invariably "see" the host name even on the Pixel.

Can't fathom it, but don't need to 'cos... IP

[robkyf]

I’m just appreciative of the help and the new knowledge that comes with it.

Self-diagnosing the source of and solution to a typical ‘it was working 5 minutes ago and I haven’t touched anything’ tech problem can be mystifying if your understanding and frame of reference is limited.

Just one of the reasons why I’ve found the willingness of the members of this forum to offer their time to help so great!