Server Version#: 1.27.1.5916
When connecting to remote/local servers the plex web client will frequently error out when using linux. I was able to track this down to systemd-resolved taking forever to return results for the plex.direct domain. systemd-resolved is querying the plex.direct SOA as part of it’s process and receiving a timeout. systemd-resolved will eventually return results, but it takes 30 seconds before it gives up on the SOA record. To work around the issue with this domain I have to disable systemd-resolved altogether.
Why does plex.direct timeout when querying the SOA record? it’s required on every domain, and it’s hard to imagine I’m the only one who has problems because it’s missing. Even a blank record would be better than a timeout. I’ve been running into this issue on new builds/installs for over a year now, it’s annoying.
dig @ns-plexdirect.plex.tv SOA plex.direct
; <<>> DiG 9.16.30 <<>> @ns-plexdirect.plex.tv SOA plex.direct
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
