# 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:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [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/1 "2019-02-03T17:10:33Z")

</div>

Originally published at: [https://pi-hole.net/2019/02/03/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/](https://pi-hole.net/2019/02/03/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/)

We’re always happy when we can release a new version of Pi-hole, so today we’re announcing v4.2 of Pi-hole. Thank you to to [our patrons](https://www.patreon.com/pihole) and everyone else who continue to [support us](https://pi-hole.net/donate/). Along with many **other things** , we’ve [merged in the upstream code from **`dnsmasq` v2.80**](https://github.com/pi-hole/FTL/pull/401). For anyone who doesn’t know, _FTL_DNS (`pihole-FTL`) is our fork of `dnsmasq`.

# Highlights

## New Blocking Mode

We’ve added a new [blocking mode](https://docs.pi-hole.net/ftldns/blockingmode/) ([`NODATA`](https://github.com/pi-hole/FTL/pull/433)), where blocked requested are replied with a status code of `NOERROR` and `A` / `AAAA` records are empty. It’s unclear if there are advantages to this mode over others, but you’re welcome to experiment with it.

## Shared Memory

In preparation of the [new API we are working on](https://github.com/pi-hole/api), _FTL_DNS will now [store its data in a shared-memory space](https://github.com/pi-hole/FTL/pull/429), so that the API can come in and read from that memory to fulfill requests. In short, this means _FTL_DNS will be even lighter as it doesn’t have to care about sending the statistics to some requester. Instead, it will concentrate on generating the statistics and the API can read FTL’s data directly, resulting in reduced delays in the API.

## wpad Vulnerability Fix

We [previously mentioned](https://pi-hole.net/2018/09/10/mitigate-a-new-cert-vulnerability-598349-with-an-entry-in-etc-hosts/) how you could work around a vulnerability regarding `wpad` entries. This fix is now in place as suggested by `dnsmaq.conf.example`.

## Fixes And Tweaks

- We updated SQLite to 3.26.0
- We fixed the query status if a forwarded query was partially replied to from the cache
- We now prevent multiple static DHCP entries with same IP
- And [more…](https://changes.pi-hole.net)

## Docker Version Also Updated

We heard your feedback and we made sure to coordinate better to release our traditional install and our Docker install at the same time.

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [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/2 "2019-02-03T17:10:34Z")

</div>



---

<div class="post-metadata">

**Author:** ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)\
**Post date:** [February 3, 2019, 8:32pm UTC](https://discourse.pi-hole.net/t/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/16763/3 "2019-02-03T20:32:33Z")

</div>



---

<div class="post-metadata">

**Author:** ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)\
**Post date:** [February 3, 2019, 9:52pm UTC](https://discourse.pi-hole.net/t/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/16763/5 "2019-02-03T21:52:03Z")

</div>

_“NODATA responses have to be algorithmically determined from the response’s contents as there is no RCODE value to indicate NODATA. In some cases to determine with certainty that NODATA is the correct response it can be necessary to send another query.”_

---

<div class="post-metadata">

**Author:** ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)\
**Post date:** [February 3, 2019, 9:54pm UTC](https://discourse.pi-hole.net/t/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/16763/6 "2019-02-03T21:54:03Z")

</div>

And I think there is some confusion, `domain.tld` is a domain, `sub.domain.tld` is also a domain. NXDOMAIN does not stop at the top level, or any level, it is a response that the requested domain does not exist. You can NXDOMAIN `my.domain.tld` and still have a valid `domain.tld` query and response.

---

<div class="post-metadata">

**Author:** ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)\
**Post date:** [February 3, 2019, 9:55pm UTC](https://discourse.pi-hole.net/t/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/16763/7 "2019-02-03T21:55:36Z")

</div>

```bash
dschaper@Mariner:/c/Users/DanSchaper$ dig blue.pi-hole.net

; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> blue.pi-hole.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55207
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;blue.pi-hole.net. IN A

;; AUTHORITY SECTION:
pi-hole.net. 3600 IN SOA dina.ns.cloudflare.com. dns.cloudflare.com. 2030049905 10000 2400 604800 3600

;; Query time: 22 msec
;; SERVER: 192.168.100.2#53(192.168.100.2)
;; WHEN: Sun Feb 03 13:54:58 STD 2019
;; MSG SIZE rcvd: 107

dschaper@Mariner:/c/Users/DanSchaper$ dig pi-hole.net

; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> pi-hole.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21280
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;pi-hole.net. IN A

;; ANSWER SECTION:
pi-hole.net. 300 IN A 206.189.252.21

;; Query time: 439 msec
;; SERVER: 192.168.100.2#53(192.168.100.2)
;; WHEN: Sun Feb 03 13:55:02 STD 2019
;; MSG SIZE rcvd: 56

```

---

<div class="post-metadata">

**Author:** ![zahni](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/z/13edae/32.png) [@zahni](https://discourse.pi-hole.net/u/zahni)\
**Post date:** [February 6, 2019, 7:27pm UTC](https://discourse.pi-hole.net/t/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/16763/9 "2019-02-06T19:27:24Z")

</div>

I switched to "nodata", because the Safari browser on my ipad often stuck in reloading pages (i have to close the current browser session or switch the tab). Nodata looks better to me. And the Safari is faster at all.  
The current problem with 4.2: The GUI won't longer log blocked sites correctly...

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [February 6, 2019, 7:30pm UTC](https://discourse.pi-hole.net/t/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/16763/10 "2019-02-06T19:30:53Z")

</div>

> [@zahni](#):
>
> The current problem with 4.2: The GUI won’t longer log blocked sites correctly…

This is known and will be fixed by FTL v4.2.1 which is about to be released

> <https://github.com/pi-hole/FTL/pull/497>
>
> Release fixing two issues:
> 
> \- Blocking status display for \`NODATA\` and \`NXDOMA…IN\` blocking modes
> \- File permission issues when using shared memory on systems that lack Linux capabilities support
> 
> It also adds in a new feature:
> \- Report both the user \`pihole-FTL\` \*\*started\*\* as and the user \`pihole-FTL\` \*\*crashed\*\* as in case it crashes and generated a crash ticket in \`pihole-FTL.log\`

---

<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.

---

<div class="post-metadata">

**Author:** ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)\
**Post date:** [March 4, 2019, 12:55am UTC](https://discourse.pi-hole.net/t/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/16763/12 "2019-03-04T00:55:20Z")

</div>



---

<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:** [March 5, 2019, 7:30pm UTC](https://discourse.pi-hole.net/t/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/16763/13 "2019-03-05T19:30:16Z")

</div>

A post was split to a new topic: [Lighttpd config gets updated](https://discourse.pi-hole.net/t/lighttpd-config-gets-updated/18058)