BUG Report: "DNS-based Filtering" blocks Netflix on Android

[lamp159]

This could seem weird, and it is. But I did many tests and I can confirm that "DNS-based Filtering" (ASUS TR-AC66U) blocks Netflix on Android devices. It does not happen in Windows machines.
This happens for any filter. I thought that it would not happen for "Comodo Secure DNS" but it happens too.
This happens since always, I think. Currently I'm running 376.47 (Merlin).
Turning off "DNS-based Filtering" solves the Netflix problem in Android devices (any version). This does not happen in Netflix for Androis 3.1.2 an previous versions, but since some version, up to the current 3.7+ this problem is true.
I don't know what Netflix changed in the app, and I don't know why "DNS-based Filtering" does not allow Netflix streaming (you can access the main UI, and select a profile, but you cannot play any video.
Weird, right?
Now I have "DNS-based Filtering" turned off, which is a bad thing. I have children, and it is so easy (even without looking for it) end in a scary page.
If there is any way this can be fixed in a future version of the firmware, it would be great.

 

[highwire]

This could seem weird, and it is. But I did many tests and I can confirm that "DNS-based Filtering" (ASUS TR-AC66U) blocks Netflix on Android devices. It does not happen in Windows machines.
This happens for any filter. I thought that it would not happen for "Comodo Secure DNS" but it happens too.
This happens since always, I think. Currently I'm running 376.47 (Merlin).
Turning off "DNS-based Filtering" solves the Netflix problem in Android devices (any version). This does not happen in Netflix for Androis 3.1.2 an previous versions, but since some version, up to the current 3.7+ this problem is true.
I don't know what Netflix changed in the app, and I don't know why "DNS-based Filtering" does not allow Netflix streaming (you can access the main UI, and select a profile, but you cannot play any video.
Weird, right?
Now I have "DNS-based Filtering" turned off, which is a bad thing. I have children, and it is so easy (even without looking for it) end in a scary page.
If there is any way this can be fixed in a future version of the firmware, it would be great.

I had the same issue, except it wasn't the router. Around the same time, a revised version of the Netflix app was released. After updating, I had the same bebhavior you described. I had to wipe out the Neflix cached application data on my mobil device. Once I did that and re-entered my login credentials, everything worked properly again.

 

[lamp159]

I had the same issue, except it wasn't the router. Around the same time, a revised version of the Netflix app was released. After updating, I had the same bebhavior you described. I had to wipe out the Neflix cached application data on my mobil device. Once I did that and re-entered my login credentials, everything worked properly again.

I tried many wipes, complete clean up of the Netflix app, etc.
The only thing that fixed the problem was disabling the filter option in the router.
Which firmware are you running in the router and which configuration in the DNS filter?
Of course, in my case, devices in the exclude list (regarding DNS filtered) could run any Netflix version without any problem.

 

[RMerlin]

Could possibly be Netflix clamping down on people going around regional limitation by using a third party DNS.

 

[highwire]

I tried many wipes, complete clean up of the Netflix app, etc.
The only thing that fixed the problem was disabling the filter option in the router.
Which firmware are you running in the router and which configuration in the DNS filter?
Of course, in my case, devices in the exclude list (regarding DNS filtered) could run any Netflix version without any problem.

RT-AC66U with 376.47. I have DNS filtering set up with a global filter, and the DNS entries set up for Unblock-us. Some devices that don't need Unblock-us are set up with no filtering. No issues.

 

[rogern]

Happened to Poivy a SIP program to call from eighter PC or phone.

Zero credit and zero in contact list, after disable it it came up as before.

 

[lamp159]

Could possibly be Netflix clamping down on people going around regional limitation by using a third party DNS.

Not in my case, because Netflix is supported in my Country.
Windows devices were always OK.
The problem was with all Android devices (different versions, different architectures, same problem even after total ROM wipe and starting fresh, in the case of the MK808. Same problem with LG G3 or any other Android device) since some Netflix version and above.
The only solution was disable DNS filtering. If I keep the DNS filtering, and add a device to the "white list" (do not filter), then it works fine. This I think clearly confirms the problem is in the router, in the DNS filtering feature, since Netflix for Android version > 2.1 (or so).

Again: I'm not using any kind of IP trick. Netlfix is legal and fully supported in my country. I have no regional limitation at all.

Maybe Netflix for Android is (in newer versions) including (for whatever reason) calls to URLs that for some reason are banned by the router DNS Filter feature (any of the options)? This could be why it does not work.

 

[Muyfa666]

RMerlin, this sounds a bit like my issues in the other thread, or did I misunderstand?

 

[bplv]

Not in my case, because Netflix is supported in my Country.
Windows devices were always OK.
The problem was with all Android devices (different versions, different architectures, same problem even after total ROM wipe and starting fresh, in the case of the MK808. Same problem with LG G3 or any other Android device) since some Netflix version and above.
The only solution was disable DNS filtering. If I keep the DNS filtering, and add a device to the "white list" (do not filter), then it works fine. This I think clearly confirms the problem is in the router, in the DNS filtering feature, since Netflix for Android version > 2.1 (or so).

Again: I'm not using any kind of IP trick. Netlfix is legal and fully supported in my country. I have no regional limitation at all.

Maybe Netflix for Android is (in newer versions) including (for whatever reason) calls to URLs that for some reason are banned by the router DNS Filter feature (any of the options)? This could be why it does not work.

Were you ever able to resolve this problem? I just started trying to use the feature with my daughter getting a tablet for Christmas and needing to lock down the network a bit more.

Netflix works when DNS filtering is off (either globally or for the android devices) but stops working when it is on. The diagnostics inside netflix report nw-2-5 errors connecting to the netflix servers or the internet. Although all the rest of the internet connections work fine.

I want her to be able to use netflix, but still lock out lots of web sites with opendns.

 

[lamp159]

>>Were you ever able to resolve this problem?

Yes.. sort of...
I have:
"Enable DNS-based Filtering" = ON
"Global Fiter Mode" = Router
In the "Client list", the hosts I want with "No Filtering" (i.e. my machine)
In the "Wan Settings", I've configured OpenDNS servers: 208.67.222.123 and 208.67.220.123, which are the servers using their predefined filters (FamilyShield).
Netflix is working fine (windows, android, etc.), and "FamilyShield" is active for the machines not it the "Client List" hosts configured with "No Filtering".

HTH!

 

[PaddyPDX]

In the last two weeks I have also come across this same issue with iOS devices. I posted about it here but just saw this thread from a couple of years ago. Does anyone know is there is a fix for this yet? I too rely on this for my young daughter's devices.

Talking to Netflix customer support is like pouring acid on my eyeballs.