Plex.direct - Unbound DNS - 21.7.1

Started by bunchofreeds, August 12, 2021, 03:15:12 AM

Previous topic - Next topic
Quote from: bunchofreeds on August 12, 2021, 10:20:57 PM

Specifically what others options you set within Blocklists.
Did you 'enable' blocklists
Did you choose a DNSBL
Did you restart the Unbound DNS Service

Also did you change anything on the plex client or server side

Thanks for any further help

I have it configure the same way and works perfectly. No changes on Plex.

Quote from: Nnyan on August 12, 2021, 07:41:31 AM
... Plex remote access will not work unless I can figure out how to do this.

As far as I know, for remote access only port 32400 is needed. I've not changed anything for the certificates so far. And remote access is working just fine (at least from native apps, usually not using app.plex.tv)

Quote from: Nnyan on August 12, 2021, 07:41:31 AM
I have been working on trying to get this done myself.  Plex remote access will not work unless I can figure out how to do this.

This is not strictly related to remote access. You only need to forward and allow the proper port on the FW for that to work. The unbound setting is needed for Plex clients in your internal network that are using Unbound as DNS server.

You are correct, it's really two separate issues.  For what ever reason opnsense does not open ports on my new AT&T gigabit connection (it was fine on Comcast's gigabit).  But I have no issues opening ports if I switch to Unifi USG, Palo Alto PA-220 (or even my Orbi RBK853 when in router mode).  I can confirm the port is open by external scans (shows up on the other devices and blocked with OPNsense.

For completeness (now that 21.7 has removed the Unbound Custom options from the GUI), the way I have continued to use the GUI to address this is as follows:

Under System, Administration, Alternate Hostnames: plex.direct otherhost (where other hosts are separated by spaces)
Under Services, Unbound DNS, Blocklist, Whitelist Domains: plex.direct
Under Services, Unbound DNS, Blocklist, Private Domains: plex.direct

This works well for me.  It pays to note that the reason I have it under both whitelist and private is I found it solved a problem when connecting to a remote plex server (not my own) which was reporting indirect connections.

For those of you missing the aforementioned way of doing this via custom options, that can still be done manually by editing /usr/local/etc/unbound.opnsense.d instead.

Hope that helps someone out there!

Marshalleq