I’m attempting to download a movie (Sicario) for offline viewing, but the download immediately fails when I attempt. So far I’ve tried: Restarting the server, restarting my device, force stopping/clearing cache for the Plex app.
Ah, so if I understand correctly, if I were to set a record on my PiHole (local DNS resolver within my LAN) pointing plex.direct to the IP of my PMS, that should fix it?
To disable a security feature on your whole network because Plex can’t implement something correctly? That does not sound nice. Also this block from that link it is a bit strange:
I do not have control of the configurations of all devices in my network. This is very unfortunate, but it is like that. Most devices are implemented in a blackbox/appliance way and the user has no way to change anything. So assuming all devices in my network are safe therefore I can disable a security feature sounds a bit iffy.
This hasn’t anything to do with “implementing something correctly”. In fact it is the protection which is “misfiring” because it is usually implemented in a too simplistic manner, so it is triggered by Plex’s completely legitimate use of DNS.
The protection is not disabled in general, but only for one particular domain name.
Peruse the linked article for background information.
To anyone else who encounters this thread with a similar issue:
My home setup uses a UDM Pro as a router. I have some iptables rules set up on the UDM Pro to force captive DNS to the DNS server of my choice. I do this so that I can force devices which do not obey the DHCP defined DNS servers to still use the defined DNS servers, even if they want to.
Simply put, I am able to force all the devices on my LAN to use my DNS server, whether they want to or not. My DNS server is a PiHole. I observed that when I changed my DNS server from my PiHole to a public DNS server, the issue went away.