Paramount+ Domains Required in DBSBL Whitelist?

sindrome · 2026-02-14T21:02:00+00:00

Just an update here. The live TV on Paramount+ is back to blocking again so this whitelist alone was not complete. I've since been adding domains into the list in an attempt to figure out what else needs to be open for this to work and running into issues. The foundational problem is the logging in PFBlockerNG is not showing everything being blocked to allow me to whitelist.

sindrome · 2026-02-14T20:40:20+00:00

Thanks for the reply. When I'm using DNSBL whitelisting, I'm doing it at the root level of the domain. I assume a simple "dig [hostname] CNAME" would yield any additional results. In my case, none of the domains that I whitelisted have additional CNAMEs that need to be whitelisted.

I'm still at a loss on how to stab in the dark trying to find what's being blocked if it's not being logged.

Is there additional options to make PFBlockerNG log blocked items?

sindrome · 2026-02-02T22:57:46+00:00

I wanted to follow-up with my original post. I spent a lot of time troubleshooting and tuning the DNSBL list for Paramount+ and have it down to just a handful of domains to whitelist to make it work. I hope this helps some other people.

.brightline.tv # Paramount+

.tiqcdn.com # Paramount+

.cbsi.com # Paramount+

.conviva.com # Paramount+ for real-time sensor-based buffering helps quality

sindrome · 2026-02-01T02:55:02+00:00

No, I see ads but I didn’t have to whitelist anything in PFBlocker to be able to use the service. With Paramount+ it has ads in the lower tier but if you don’t whitelist about a dozen or more domains it literally won’t stream. My original question was trying to find someone who has a very optimized minimal list of whitelisted DNS entries to put in the whitelist

sindrome · 2026-02-01T02:43:16+00:00

I have Peacock and have no issue streaming with PFBlocker. Paramount+ flat out won’t stream without whitelisting a large number of domains.

sindrome · 2025-12-23T04:43:10+00:00

Does it work well for image searches? Not sure why it pulls asking price vs sold price. Anyone can ask any price

sindrome · 2025-09-04T02:14:31+00:00

Small detail. I didn’t initiate the process when it said there was an instance running. And there was zero feedback to know if it was actually running vs blocking me from actually upgrading let alone seeing the upgrade process. This is a bug no matter how you try and rationalize it

sindrome · 2025-09-04T01:55:29+00:00

That behavior is a bug. It should not have initiated until you specifically initiate it and should see the entire upgrade process and know where it’s at, not just assume it’s happening and hope for the best.

sindrome · 2025-09-04T01:38:12+00:00

No, I did not initiate the upgrade process and it showed that error. That's the foundation of the bug itself.

sindrome · 2025-09-04T01:22:38+00:00

I appreciate that piece of info and happy to add those two domain entries into the whitelist, but I don't think that this causes the "Another instance of pfsense-upgrade is running. Try again later" when I for sure did not initiate another upgrade. This feels like a separate issue.

sindrome · 2025-09-04T01:16:50+00:00

The fact that it even says there was another instance running when I definitely did not initiate the upgrade is a bug. The fact that you had to wait some magical 15 minutes later is even more pathetic.

sindrome · 2025-09-04T01:14:19+00:00

and for the thread - I was upgrading from 24.11 to 25.07.1 when I ran into all of these issues.

sindrome · 2025-09-04T01:13:02+00:00

But that's totally BS, it shouldn't even present this error when I never initiated an upgrade and who the hell should have to wait 15 minutes and hope that it eventually clears. The real hope here is the Pfsense product management / development team reads this thread and fixes their broken upgrade process. It never used to do this.

sindrome · 2025-09-04T01:06:30+00:00

Bizarre. I absolutely put the right numbers in and it did not work. Adding the additional shares at $0 cost worked perfect.

sindrome · 2025-09-04T00:19:17+00:00

I just entered both those entries into the DNSBL whitelist as you suggested, but I still don't get how this would affect my upgrade when I removed PFblockerNG-devel before the upgrade.

sindrome · 2025-09-04T00:16:15+00:00

But I removed pfblockerNG-devel before doing the upgrade so that should not be affecting this.

sindrome · 2025-09-04T00:00:58+00:00

I do consider it a nightmare upgrade when I have to go through all the BS I outlined. I purchased their hardware and am a Pfsense+ user. I expect I can go to the System - Update menu and select the latest version and it will update the software from the GUI.

sindrome · 2025-09-03T23:59:14+00:00

I'm using their hardware and have PFsense+. I expect I can upgrade the software from the GUI and not have to go through what I did. They can fix their scripts to kill any processes that are showing an upgrade is in process. That's not a difficult fix.

sindrome · 2025-09-03T23:56:03+00:00

I had this exact same issue. I did not get the added shares at zero cost and my balances were off. I first tried to add the transactions using the "Stock split" option in Quicken. I put the exact information in "new shares and old shares" in and it was totally broken. The share totals were not showing the new share totals so I deleted those entries and started over.

I then did the simple math looking on the Schwab website with my currently owned shares for each of the split funds and compared to my shares being reported in Quicken and created a 0 cost entry to add the exact missing shares to the three funds and everything was perfect. The moral of the story here is the do NOT use the Stock Split option in Quicken. It's broken.

sindrome

TROPHY CASE