AdGuard Personal DNS, using the DoT protocol on a FRITZ!Box 5970 AX, using AdGuard browsing security and the AdGuard DNS filter.
Traceroute to AdGuard DNS
No response
Issue Details
When streaming from the Binge app on a Samsung smart TV, after approximately 10mins of stream time, the Binge app will lock up over a period of a few minutes to the point the entire TV is unusable, entirely unable to be turned off unless the power for the tv is cycled at the GPO. I have been experiencing this for about a year now.
After some time fault finding the issue, I think I’ve found the culprit.
I first confirmed that by using Google DNS (8.8.8.8) on the Smart TV that the issue no longer existed. This was tested over 3 days with no issues. Approximately 9 hours of play time.
I then made a seperate server on AdGuard DNS, not enabling any filters, and streamed 1.5hrs of movie, with the issue not occurring.
After enabling browsing security, and the AdGuard DNS filter, the Binge app stopped working, but instead of locking up, showed an error message, stating it couldn't access the following domain: vod-hevc-uhd-drm1-cf.foxtelgroupcdn.net.au.
What’s weird is that the domain doesn’t appear as blocked in the query logs.
After unblocking this domain in the user rules, I haven’t experienced the issue again after streaming around 3hrs of media.
I no longer have the issue, but figured it would be worthwhile adding it to the AdGuard DNS allowlist to prevent further people having this issue.
It seems to be widely discussed on the Australian Whirpool forums, and Reddit when searching online for the Binge app freezing.
Expected Behavior
Binge app on Samsung smart TV streams without issues.
Actual Behavior
Binge app streams for around 10mins then entirely locks up the TV.
Platform
Other
Protocol
DNS-over-TLS
Do you use AdGuard app?
No I don't
Your configuration
AdGuard Personal DNS, using the DoT protocol on a FRITZ!Box 5970 AX, using AdGuard browsing security and the AdGuard DNS filter.
Traceroute to AdGuard DNS
No response
Issue Details
When streaming from the Binge app on a Samsung smart TV, after approximately 10mins of stream time, the Binge app will lock up over a period of a few minutes to the point the entire TV is unusable, entirely unable to be turned off unless the power for the tv is cycled at the GPO. I have been experiencing this for about a year now.
After some time fault finding the issue, I think I’ve found the culprit.
I first confirmed that by using Google DNS (8.8.8.8) on the Smart TV that the issue no longer existed. This was tested over 3 days with no issues. Approximately 9 hours of play time.
I then made a seperate server on AdGuard DNS, not enabling any filters, and streamed 1.5hrs of movie, with the issue not occurring.
After enabling browsing security, and the AdGuard DNS filter, the Binge app stopped working, but instead of locking up, showed an error message, stating it couldn't access the following domain:
vod-hevc-uhd-drm1-cf.foxtelgroupcdn.net.au. What’s weird is that the domain doesn’t appear as blocked in the query logs.After unblocking this domain in the user rules, I haven’t experienced the issue again after streaming around 3hrs of media.
I no longer have the issue, but figured it would be worthwhile adding it to the AdGuard DNS allowlist to prevent further people having this issue. It seems to be widely discussed on the Australian Whirpool forums, and Reddit when searching online for the Binge app freezing.
Expected Behavior
Binge app on Samsung smart TV streams without issues.
Actual Behavior
Binge app streams for around 10mins then entirely locks up the TV.
Screenshots
Screenshot 1:
Additional Information
No response