@Plex_in_RV, that value is a configuration entry for the dnsmasq service that is installed on the router I am using. It is using an override address capability which indicates the domain name plex.tv should point to the local host. This allows an unconnected instance to be able to resolve the hostname plex.tv (no more UnknownHostException exceptions since it points to itself) – and by chance, the Plex Media Server is able to start.
On a related note, this issue still exists with the most recent Plex Media Server version (1.13.5.5291) with default settings. I do see a note in the most recent change log which indicates:
Allow picking a specific network address to bind to (#8492)
I will try taking advantage of this option to see if it prevents a need for this workaround. If I find anything new, I will update my findings here.
