What I've learned about Paramount + and unbound DNS

Follow

Dave H

• August 25, 2022 15:33

I was using unbound DNS on my three network segments PCs, Phones, IOT.

Many times the Paramount + streaming app (Roku) spun the circle of death then prompted that it looked like I was using a VPN.  I found a post from someone who had spoken to their tech support and the post stated that Paramount + suspects any DNS query that is not from my ISPs DNS server.  I turned off unbound DNS for my entire IOT segment (still using DNS Booster though).

The Paramount + streaming issue has not presented again (after a week of daily use)

0

• 

  Firewalla

  • August 25, 2022 16:27

  This is a seriously strange problem. if you change the DNS to say 1.1.1.1 will it work? What you use DoH? 

   

  0

  Comment actions Permalink
• 

  Dave H

  • August 25, 2022 17:00

  I won't be re-configuring or doing additional testing.  No to DoH.  All I know is it had been happening night after night.  Then I read the following post and realized it could be unbound dns causing the issue.

  Solved: Solution to Paramount Plus App not streaming conte... - Samsung Community - 2023984

  After turning off unbound on my IOT segment the issue hasn't presented the last 4 nights.

  0

  Comment actions Permalink
• 

  Firewalla

  • August 25, 2022 17:52

  So, ISP's are messing with DNS records ... 

  0

  Comment actions Permalink
• 

  ridv

  • June 18, 2023 20:30
  • Edited

  I can confirm that changing WAN DNS to 1.1.1.1 allows Paramount Plus to work. (Thanks for the hints on the possible solution).

  Without this change I was consistently getting error 6040. I'll look for a less invasive solution when I have some time and post it back here.

  0

  Comment actions Permalink
• 

  Firewalla

  • June 18, 2023 20:47

  Did you have unbound before this? 

  0

  Comment actions Permalink
• 

  ridv

  • June 19, 2023 02:34
  • Edited

  I did not. But I did enable it after reading up on it and paramount + still works after enabling it and waiting a while before trying it out.

  Update: And now it works without setting 1.1.1.1. Who understands how these streaming services work? In any case, if anyone hits the 6040 error, a solution is to turn off Unbound and set the WAN DNS to 1.1.1.1, at least temporarily.

  0

  Comment actions Permalink
• 

  Dave H

  • June 20, 2023 13:22

  When I originated this post I had just begun using unbound.  I saw an external post relating Paramount Plus issues to a DNS configuration so I stopped using unbound on my IOT segment.  I haven't had the Paramount Plus issue since.  I am using a Roku to stream Paramount Plus.  I'm not a network engineer, but I'd like to understand how unbound affects this service.

  0

  Comment actions Permalink
• 

  David Rothenberger

  • June 21, 2023 17:31

  I use both Roku and a Chromebook to stream Paramount Plus, and I have Unbound in use for all my network segments, including these devices. I've never had any problems with Paramount Plus.

  I would also love to understand how unbound is messing with Paramount Plus.

  0

  Comment actions Permalink
• 

  Jeff K

  • June 22, 2023 13:12
  • Edited

  I use Unbound on a Purple, but I also run my own private DNS through Ad Guard Home via Homeassistant.  Not sure it makes any difference, running both.  I have not had any issues viewing Paramount+ or any other streaming service.. I also did my checks to see what roku / plex url's needed to be unblocked ect... and have had no issues with any services.

  0

  Comment actions Permalink

Please sign in to leave a comment.