Yep… That’s what was happening to me before. Can you log into your router? 192.168.1.1, check the system logs. Do you see a dnsmasq warning (possible DNS-rebind attack)?
I am getting the same errors on my router with the dnsmasq warnings. Has anyone found a solution to this?
I’ve fallen down all of the crazy rabbit holes on these threads, but I’ve come to the conclusion that my new G3100 router just doesn’t like Plex. I am receiving the same issues as well:
Event-Type: dnsmasq
Log Level: warning
Details: [SYS.4][SYS] possible DNS-rebind attack detected
When I logged into the router, I didn’t see a way to change its DNS server, but I did it on the Plex server and it didn’t make a difference. What’s weird is that this only started happening recently. My son and I just watched a movie on the Smart TV from the Plex server several days ago, and just like two days ago, I can’t access the Plex server from any device.
I went through a lot of the steps–Home Protection was disabled already, DNS server stuff, trying to mess with IPv6 options…nothing works. It’s just frustrating because it did in fact work like it always has.
Probably going to open a ticket with Verizon tomorrow and see if they can do anything to get it sorted out. I will update this post if I am able to resolve. Love the router. Hate that I can’t use Plex with it
Please do. I was going to switch to Cox anyway because they could offer the best deal and Verizon has been messing around with us for awhile. But if it can get fixed, and we can’t get Cox, at least we’ll all know how to fix it.
I think it’s worth noting that this is not exclusive to Verizon as I saw issues with TP routers as well.
I didn’t have this issue with my older Verizon router though. And if I hook that one back up, Plex works fine. For some reason, it seems to not work on the G3100 router. I actually have the Cox router so I’m going to hook it up and see if I get the same issue. Or maybe Cox routers have a way to turn off the dnsmasq error stuff.
All I know is I’ve tried setting up port forwarding for my Plex server and Verizon still sees it as a dnsmasq error.
I think I got it!
I contacted Verizon via their chat and told them the error I was getting and if they could somehow whitelist the IP. They did something in the back end and my router rebooted a few times. It wasn’t until later that day where I noticed I had more people watching and saw no indirect connections.
I asked around and people said it was a lot more stable. Checked logs and saw people watching all hours of the night.
Fingers crossed this worked!
Fingers crossed but it works now. That’s amazing that it was just Verizon simply doing something small in the background. Did they ever give you a reason as to why they did it in the first place?
Appreciate the help Snackpacks!
They didn’t tell me exactly what they did. They wanted to direct me to advanced support because right after they made the change it was not working. Weird that it took a few hours to replicate.
I do still get the DNS rebinding errors in the logs but since they applied the fix, I have had 0 reports of disconnects.
1 Like
Same problem. It’s verizion Fault and their firewall.
- download the Verizon MY FIOS app
- log in while on the same network that’s having the issue
- my fios>> internet> Devices &parental control> notifications
- find the blocked Plex and > allow access
So when I go to the FiOS app, I can follow the path to My FiOS —> Internet —> Devices and Parental Controls, but I don’t have a notifications option. I only have three options: Parental Controls, Manage Devices, and Activate Home Network Protection.
Do you have the Active Home Network Protection on? Maybe I need to turn it on and then mark Plex as safe.
That’s correct. Home network protection on. Open up notifications and allow access to Plex. If fios is blocking you it will be notified there.
So I activated the Home Network Protection, and I do see a section for Notifications. Although all of the notifications pertain to devices found on the network–there’s nothing about Plex on there or blocking access, and I can still see in the System Logging of the router the following eror:
dnsmasq
warning
[SYS.4][SYS] possible DNS-rebind attack detected: 192-168-1-215.3.plex.direct
I also get this error sometimes too:
[SYS.4][SYS] possible DNS-rebind attack detected: 192-168-1-215.abcdefghijklmnopqrstuvwxyz012345.plex.direct
Weird that it’s cycling through the alphabet on that specific error.
The Plex server is connected right now, but I bet when I check it in about an hour or two, it’ll be disconnected. I’ll just have to contact Verizon and see if there’s something they can do on their end I guess.
Advanced settings> reboot router. When Plex gets kicked off again you should check notifications again and allow access. Do you have a VPN? ie. expressVPN. Try using that to get behind verizion. If you do contact Verizon ask then how to get something whitelisted.
The location to disable the rebind protection is in a weird spot; this fixed my issue I was having which was the exact same.
https://192.168.1.1/dns_server.htm
Whatever your IP is replace it above;
!
I must have missed this option, thank you very much for pointing that out!!!
You can also go to Advanced --> DNS Server to find this page. This solution works fine for me for now but in general this may not be the most desirable result but seems to work…
1 Like
I haven’t had any issues personally but all of my entries sit behind SWAG/NGINX though in docker containers locked away.
Already had that option checked and I was still getting that error. Found that when I was just clicking on everything in the Advanced area…lol. Doesn’t seem to stop the plex server from being seen as an attack, unfortunately. Not for me at least. Anyone else try this and it worked for them?
EDIT: What is SWAG/NGINX btw?
Rebooted router while the Home Network Protection was on. The only difference in notifications was that it showed that I had turned the protection off and then on again at different points. But I’ve had my friend try to access my plex server, and it’s still inaccessible.
It’s just weird because sometimes the server works fine, and other times it just shuts down. Like my friend was able to watch movies on Saturday, but Sunday it wasn’t working. I was watching my server and it was up on Saturday, but went down on Sunday for whatever reason.
It’s just annoying because it seems to be up or down whenever it wants to.
