When configuring plex for remote access in an environment with frequently cycled IP’s, at time plextv will have an older non-functional IP pointing to the remote deployment. Add a feature to allow the administrator to set a domain name to the install.
You can already do this, the “custom server URL” field supports domain names.
A changed public IP should get noticed by plex.tv after 30 minutes.
The bigger issue are usually the DNS servers of your clients, which needs to get an updated record of your server’s FQDN.
If you are using your ISP’s DNS server, some don’t update fast enough. If you encounter such a situation, try setting the DNS field in your router to the public DNS service of Google. (8.8.8.8 and/or 8.8.4.4)
Agreed on the DNS resolution front however if someone is using a mobile client via plex.tv & have their DNS pointing to something modern, they’re still dependant on Plex reporting the servers new IP address to Plex.tv which could take up to 30 minutes.
If you use a DDNS service with faster updates, you can add that address to the custom server URL’s, and the clients will then connect through that address (which is presumably updated faster) when the *.plex.direct address fails. Only downside: you’ll have to get your own certificate for that domain name, or accept insecure connections.
I think the topic can be closed since this feature already exists? Or moved to the Remote Access subforum to continue discussion there?
1 Like
Indeed.
This topic was automatically closed after 90 days. New replies are no longer allowed.
