Why no Parental Controls? ... tech is already in PH

[Ltek]

People have been asking for these features for years (especially since Covid). It looks like all the underpinnings are there to make this happen (groups, blacklists, timers, etc).

We need to have this in the native UI (without hacks).

It could be a few basic features added and we would be there. Like...

"Apply Blacklist to Group - during time frame"
-- only allows specific sites be contacted, perfect for home school so older kids who need larger freedom to do research, etc but stop them from going to YouTube or game sites during school hours, or on dedicated 'school devices'

"Block all Group activity - during time frame"
-- no internet allowed, perfect for limiting kids device use and home school

"Apply Whitelist to Group - during time frame"
-- only allows specific sites be contacted, perfect for home school

[yubiuser]

Why no Parental Controls?

Simple, but blunt answer: Because nobody has written the code so far.

You might want to support this feature request:

Timed DNS queries, block DNS based on time

Hi pi-hole Firstly aplogies if I'm not doing this correctly Title timed DNS queries Block DNS based on time We have broadband which is limited during the day, and unlimited at night We currently block apple update servers all the time Would be helpful to have a special list call it a grey or yellow list Which would block always except for certain times I would propose having a general time setting and allowing domains to be turned on /off on the fly I am a developer so would be happy to…

[Bucking_Horn]

Pi-hole is not a parental control system.
It is a DNS filter.
As such, it relies on the explicit intention of its users to filter DNS requests.

By-passing it is as easy as manually configuring a public DNS server on a device or switching from wifi to mobile network on a tablet or smartphone.

[lupinehorror]

as mentioned i think most tech savvy youngsters (which is presumably most of them these days) could easily circumvent pi-hole once they knew what the issue was. dealing with it on a client/device level seems like it would be more effective.