DNS Rebind Protection detected

The Plex for Windows app just died on me 2 days ago.
I didn’t modify any settings on this computer and now its whining about “DNS Rebind protection”.
Changed my DNS servers to google dns but it didn’t help.
All other players work fine.

@kript0x said:
The Plex for Windows app just died on me 2 days ago.
I didn’t modify any settings on this computer and now its whining about “DNS Rebind protection”.
Changed my DNS servers to google dns but it didn’t help.
All other players work fine.

Switching to google DNS is actually not a bad idea. But DNS rebind protection is done in your local DNS resolver i.e. usually the one built into your router.
If you can find a way to access the special properties of this, you may be able to tell it to make an exemption with the domain plex.direct and allow DNS rebinding for it. Otherwise you won’t be able to use Secure Connections when on the same local network as the Plex server.
https://support.plex.tv/hc/en-us/articles/206225077-How-to-Use-Secure-Server-Connections

@OttoKerner said:

@kript0x said:
The Plex for Windows app just died on me 2 days ago.
I didn’t modify any settings on this computer and now its whining about “DNS Rebind protection”.
Changed my DNS servers to google dns but it didn’t help.
All other players work fine.

Switching to google DNS is actually not a bad idea. But DNS rebind protection is done in your local DNS resolver i.e. usually the one built into your router.
If you can find a way to access the special properties of this, you may be able to tell it to make an exemption with the domain plex.direct and allow DNS rebinding for it. Otherwise you won’t be able to use Secure Connections when on the same local network as the Plex server.
https://support.plex.tv/hc/en-us/articles/206225077-How-to-Use-Secure-Server-Connections

The problem occurs with both local (same computer) and remote (over internet) servers.
The server is configured as “Secure connections: Preferred” and not mandatory.

I don’t know of any dns rebinding options for my computer (win10) or router.

What router are you using?

@kegobeer-plex said:
What router are you using?

Something from my ISP.
It has no settings panel. But I doubt its my router since the app worked fine and I can’t & didn’t change router cfg.

Your ISP may have changed settings in the router. They tend to do stuff like that all the time.

The rebinding detection was just recently added to the app. So I guess that’s why you didn’t see it before.
Is this message preventing you from using the app, or can you dismiss it?

@OttoKerner said:
The rebinding detection was just recently added to the app. So I guess that’s why you didn’t see it before.
Is this message preventing you from using the app, or can you dismiss it?

It prevents me from using the app.

Have you checked with Secure Connections disabled? (restart server after changing)

How do other Plex client apps behave?

@kript0x: the app logs would definitely be helpful here to see exactly what is triggering the message. I’ll add more info to the logs in that area for the next app release. What is happening behind the scenes is that the app tried to resolve the a plex.direct DNS address and gets no answer back.

@kript0x: I’ve published 2.1.4.28 with the improved logging code. Please send me the logs after you try using the app.

@pombeirp said:
@kript0x: I’ve published 2.1.4.28 with the improved logging code. Please send me the logs after you try using the app.

I found the log settings under advanced settings.
Where are the log files located?

@kript0x said:
Where are the log files located?

https://support.plex.tv/hc/en-us/articles/201515547

@kript0x: thanks for the logs. Unfortunately they are inconclusive, so I’ll need to issue a new build to test again. In the mean time, can you enter the address https://172-17-0-46.898d9b15b3d245a68d0439549051574e.plex.direct:32400/identity on your web browser (when you’re on that network) and tell me what you see? It should be something like

<MediaContainer size="0" machineIdentifier="6be519afe2ae87cfa4ecb67b4cd1a7ca5ab8ad08" version="1.0.0.2261-a17e99e"></MediaContainer>

@pombeirp Sorry for the late response,
I get a ERR_CONNECTION_TIMED_OUT in Chrome.

And

C:\>nslookup https://172-17-0-46.898d9b15b3d245a68d0439549051574e.plex.direct:32400/identity
Server:  hobo01.dnsresv6.prd.telenet-ops.be
Address:  2a02:1800:100::44:1

Non-authoritative answer:
Name:    https://172-17-0-46.898d9b15b3d245a68d0439549051574e.plex.direct:32400/identity.home
Address:  127.128.4.56

Bump.
Would really like to check out the new app.

Bump.
@pombeirp

Sorry for the silence @kript0x, I just returned from a couple weeks vacation.

Did you notice that the answer to the DNS lookup returned an address suffixed with .home. Any idea why? Maybe this is what is causing the issue?

@pombeirp said:
Sorry for the silence @kript0x, I just returned from a couple weeks vacation.

Did you notice that the answer to the DNS lookup returned an address suffixed with .home. Any idea why? Maybe this is what is causing the issue?

The app now works for me.
The nslookup doesn’t return an address with the .home suffix either.

I wasn’t specifically looking for a fix for this, but I changed my DNS servers to Google DNS today and cleaned my computer thoroughly (CCleaner + Winapp2.ini).

The app is great!

Glad to know you’re able to enjoy it now! Thanks for the feedback.