# Pi-hole v4.2 Available With Shared Memory, New Blocking Modes, And More

**URL:** <https://discourse.pi-hole.net/t/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/16763>\
**Category:** Announcements\
**Created:** [February 3, 2019, 5:10pm UTC](https://discourse.pi-hole.net/t/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/16763 "2019-02-03T17:10:33Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![mibere](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/mibere/32/18057_2.png) [@mibere](https://discourse.pi-hole.net/u/mibere)\
**Post date:** [February 7, 2019, 2:08pm UTC](https://discourse.pi-hole.net/t/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/16763/11 "2019-02-07T14:08:41Z")

</div>

Updated to 4.2.1 today, without obvious problems so far. Thanks for the new version 👍

Short side note: the following reported behavior is unchanged. As soon as the "Use DNSSEC" option is enabled the cache doesn't work anymore.

> [@Cache issue with v4.1.2?](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437):
>
> I'm on Pi-hole Version v4.1.1 Web Interface Version v4.1.1 FTL Version v4.1.2 Is there a known cache issue? The command dig +short chaos txt insertions.bind returns 0 even after hours. Even 'DNS cache insertions' in the Web UI keeps on 0 (clearing browser cache doesn't help) and also the graph on the Dashboard is abnormal regarding "Queries answered by Cache". A restart of the Pi doesn't change anything. I'm not sure, but there was no problem with v4.1.1.

---

_[View the full topic](https://discourse.pi-hole.net/t/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/16763)._