# Second level Blacklist triggered on a schedule

**URL:** <https://discourse.pi-hole.net/t/second-level-blacklist-triggered-on-a-schedule/23715>\
**Category:** Duplicate\
**Created:** [September 18, 2019, 1:45pm UTC](https://discourse.pi-hole.net/t/second-level-blacklist-triggered-on-a-schedule/23715 "2019-09-18T13:45:08Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [September 18, 2019, 2:47pm UTC](https://discourse.pi-hole.net/t/second-level-blacklist-triggered-on-a-schedule/23715/3 "2019-09-18T14:47:31Z")

</div>

> [@callumw](#):
>
> The ability to have a second set of blacklist rules that can be implemented on a schedule so to make sure all LAN traffic to/from those sites are gracefully blocked.

You can write a cron script to add these domains and remove these domains at the desired times, but this will also block those domains for all users on that Pi-Hole. A second Pi-Hole with such a script or a router that has this capability would be your best options.

---

_[View the full topic](https://discourse.pi-hole.net/t/second-level-blacklist-triggered-on-a-schedule/23715)._