NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Domain Fronting / Inability to Block Sites
All, I'm trying to block websites for my child (without Disney app, which I didn't find useful) and am having some issues. I've tested various sites to block, e..g, - discord / discordapp /...
This issue is solved
By going through the 3rd party DNS (eg OpenDNS), which was free, easy to set up and easy to add/configure in the Orbi settings, I was able to successfully block all the sites that I wanted.
Additionally, OpenDNS
- already had different tiers/levels of security with pre-screened + blocked sites
- once you choose a tier, you can add additional blocked sites
- you can also add 'always allowed' sites
- and, finally, the reporting gave me all the details that I need to actively monitor and protect my child; I can browse the list daily and identify/block any new, questionable sites
The earlier response which indicated failures between Chrome and Safari was purely a timing issue. Chrome recognized the updated settings almost immediately whereas Safari needed a couple hours (likely some caching somewhere, but it finally accepted).
Now that I'm using OpenDNS, if anyone recommends other DNS providers instead (Quad9, others), please share your thoughts.
I agree completely that Netgear's site blocking capability is too primitive and does not meet user expectations.
This may be the reason they have partnered with Disney Circle (which cleaver teenagers appear to be able to bypass with impunity, but that's another story. Google "disable disney circle" some time.)
The Orbi "logs" (in my opinion) are not a reliable method to determine how the site blocking is actually failing. They do not report actual DNS conversations. A more precise method is to capture the actual Wide Area Network (WAN) traffic between Orbi router and internet. Web site "fronting" may indeed be (yet another) way that Orbi's site blocking fails.
I'll try to set up a test tonight.
Thank you
I saw your response on the other post and attempted your test. Different site, but same test, and I couldn't make rhyme or reason what was going on.
Test browser was Safari
On test,
- didn't block on first go via direct url
- did google search via browser and then selected google result. Didn't block.
- tried url with https://. Site blocked.
- tried url again, but with http://. Site again blocked.
- after that, all bets were off. Site never blocked again.