Hi all - I’m having the exact same problem as this guy here but I use DD-WRT instead of pfSense. Plex in both the webapp and PMP show as “remote” in any situation except using my local 192.168 IP address that the server is installed on.
I’d like to be able to access plex in my own home as http://servername:32400 and have it show as nearby, instead of Remote. I’ve already tried adding the line of code to my DNSMasq setting - rebind-domain-ok=/plex.direct/ - but when I do that, it knocks my entire internet DNS offline (i.e. I can only go to sites that are in my browser’s local cache, no new ones).
My other DD-WRT settings for DNSMasq are
DNSMasq - Enabled
Local DNS - Enabled
No DNS Rebind - Enabled
And like I said, if I add that rebind-domain-ok option to the textbox below, it knocks out the entire DNS system apparently. I’ve tried saving, applying, and rebooting the router after those changes.
Can anyone help me figure out how to get this working?
@sha256 said:
And like I said, if I add that rebind-domain-ok option to the textbox below, it knocks out the entire DNS system apparently.
In my experience, this happens when your dd-wrt build is hopelessly outdated.
seek for an updated build for your device DD-WRT » Other Downloads
For reference, this is how the line looks in my ‘Additional DNSMasq Options’: rebind-domain-ok=/plex.direct/
If you have more than one line in this input field, only use Enter to generate a new line. Don’t add ; or similar to the end of lines.
Interesting. Thanks for the insight - I know I’m using a pretty old build but I have been nervous about updating since (from what I’ve heard) you have to start over with your DD-WRT config from scratch. I’ve made so many modifications over the years I don’t know how I’ll remember to re-do every single thing.
@OttoKerner I hate to ask a non-Plex question but since it sounds like you use dd-wrt yourself, can you confirm/deny for me that my fears are true; if I update DD-WRT to a modern version will I have to re-input everything by hand?
@sha256 said: @OttoKerner I hate to ask a non-Plex question but since it sounds like you use dd-wrt yourself, can you confirm/deny for me that my fears are true; if I update DD-WRT to a modern version will I have to re-input everything by hand?
I can’t answer that. But usually this is not true.
If you you want to be cautious, just go through the menu items and make screen shots.
I got around to doing the update today the most recent version for the WNDR3700v1 was - : DD-WRT v3.0-r31825 std (04/06/17) - and although the process of flashing was a rocky 2 hour experience (note to Googlers finding this thread; don’t use the “webflash.bin” file, use the factory.img file on the dd-wrt website to do the TFTP or webGUI flash; my router soft-bricked and needed to use the tftp2.exe on the dd-wrt website to ftp to the router’s default IP 192.168.1.1 and then update from there before it worked).
But then after I got the new DD-WRT working, I added the line you mentioned, Otto, and ran ipconfig /flushdns on my windows box. Immediately the text at IPADDRESS:32400/web changed from remote to nearby.
Reviving this old thread because I was in this exact same situation and I have resolved it by updating DD-WRT on my router and adding rebind-domain-ok=/plex.direct/ in my “Additional DNSMasq Options”
