Ah, this could definitely explain it!
This configuration is pretty unfortunate, since relying solely on NSS for DNS resolution means that statically-linked apps or ones that ship their own libc (such as PMS) won’t work; it’s pretty much always a good idea to have either a valid resolv.conf, or have a stub resolver listening on 127.0.0.1.
I’m very curious how this configuration ends up happening in the first place; systemd-resolvd exposes a stub resolver at 127.0.0.53, and one would naïvely expect resolv.conf to point at that on a system that uses it.
Anyway, for now, to work around this issue, I’m going to hardcode 127.0.0.53 as an additional fallback address, and add support for an env variable (FALLBACK_NAMESERVER) that’ll also be tried if set. You can build my branch if you’d like; otherwise, you can try this build, which can be dropped into the PMS lib directory. If all seems to be well, we’ll push this out in an upcoming PMS release to work around the bad configuration for people who somehow end up in that situation accidentally.
Thanks much to everyone for your cooperation.
