Differences

This shows you the differences between two versions of the page.

--- pfsense:plex [2020/12/07 09:13] – [Update DNS Resolver] peter
+++ pfsense:plex [2020/12/07 09:30] (current) – [Update DNS Resolver] peter
@@ Line 77: / Line 77: @@
 <WRAP todo>
-**TODO:**  This image is wrong.  There should only be a single **server** word, right at the top.  Remove the other one.
+**TODO:**  This image is wrong.  There should only be a single **server:** word, right at the top.  Remove the other one.
 </WRAP>
+<WRAP info>
+**NOTE: ** An alternative method is to have the following entries within the Resolver Custom option:
+<code>
+server:
+    local-zone: “plex.direct” redirect
+    local-data: "plex.direct 3600 IN A "
+</code>
+</WRAP>
+<WRAP info>
+**NOTE:**  An alternative method to overcome the DNS protection is to navigate to **System -> Advanced -> Firewall and NAT**.
+In **Network Address Translation**:
+  * NAT Reflection mode for port forwards:  **NAT + proxy**.
+While this works for remote connections, it is not everything needed to get local secure connections working, so this is not the recommended approach to take.
+</WRAP>
+<WRAP important>
+**WARNING:** When working around DNS rebinding protection this way, your apps and Plex Media Server will typically treat the connections as being from a **Remote** source.
+This can affect which streaming qualities are used, as well as trigger Remote-applicable Server Settings - Bandwidth and Transcoding Limits.
+</WRAP>
+----
 See [[PFSense:pfBlockerNG:Bypass pfBlockerNG for specific clients|Bypass pfBlockerNG for specific clients]]