# Cache issue with v4.1.2?

**URL:** <https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437>\
**Category:** Help\
**Created:** [December 24, 2018, 5:05pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437 "2018-12-24T17:05:37Z")\
**Posts on this page:** 20\
**Page:** 1

<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:** [December 24, 2018, 5:05pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/1 "2018-12-24T17:05:37Z")

</div>

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:** ![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:** [December 24, 2018, 5:09pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/2 "2018-12-24T17:09:34Z")

</div>

What is the output of: `echo ">cacheinfo" | nc 127.0.0.1 4711`

---

<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:** [December 24, 2018, 5:10pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/3 "2018-12-24T17:10:58Z")

</div>

Fresh restart of FTL and I'm showing immediate cache activity.

```auto
dschaper@nanopim1plus:~$ dig +short chaos txt insertions.bind @127.0.0.1
"25"
dschaper@nanopim1plus:~$ dig +short chaos txt version.bind @127.0.0.1
"dnsmasq-pi-hole-2.79"
dschaper@nanopim1plus:~$ pihole-FTL --version
v4.1.2

```

---

<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:** [December 24, 2018, 5:14pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/4 "2018-12-24T17:14:37Z")

</div>

Output is

> $ echo "\>cacheinfo" | nc 127.0.0.1 4711  
> cache-size: 10000  
> cache-live-freed: 0  
> cache-inserted: 0  
> ---EOM---

It seems the issue appeared in the past 24 hours (noticed it last night).

---

<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:** [December 24, 2018, 6:18pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/5 "2018-12-24T18:18:01Z")

</div>

The _Query Log_ only shows "OK (forwarded)", but no "OK (cached)" anymore.

Don't know what is happening here, but I don't have a cache anymore 🤔

---

<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:** [December 24, 2018, 6:41pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/7 "2018-12-24T18:41:44Z")

</div>

What does `free -h` show for available memory, and `df -h` for available disk space?

---

<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:** [December 24, 2018, 6:50pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/8 "2018-12-24T18:50:06Z")

</div>

```
$ free -h
              total used free shared buff/cache available
Mem: 976M 141M 703M 14M 131M 775M
Swap: 99M 0B 99M

```

and

```
$ df -h

Filesystem Size Used Avail Use% Mounted on
/dev/root 15G 1.6G 13G 12% /
devtmpfs 484M 0 484M 0% /dev
tmpfs 489M 0 489M 0% /dev/shm
tmpfs 489M 6.5M 482M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 489M 0 489M 0% /sys/fs/cgroup
/dev/mmcblk0p1 42M 23M 20M 54% /boot
tmpfs 98M 0 98M 0% /run/user/999
tmpfs 98M 0 98M 0% /run/user/1000

```

---

<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:** [December 24, 2018, 6:50pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/9 "2018-12-24T18:50:47Z")

</div>

Okay, a debug token would help as well.

---

<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:** [December 24, 2018, 6:59pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/10 "2018-12-24T18:59:06Z")

</div>

Debug token: sufehc2m6j

---

<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:** [December 24, 2018, 7:07pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/11 "2018-12-24T19:07:12Z")

</div>

Ah, here is a hint: after disabling "Use DNSSEC" on DNS tab the cache is working again.

But that option was enabled for month, without problems so far.

---

<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:** [December 24, 2018, 7:17pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/12 "2018-12-24T19:17:15Z")

</div>

> [@mibere](#):
>
> sufehc2m6j

`pihole-FTL` is still based on the 2.79 version of `dnsmasq`. There are issues with the DNSSEC implementation that are expected to be resolved when the FTL moves to the 2.8 branch of `dnsmasq`. We anticipate that happening with Pi-hole version 4.2. Until then there is the chance of unexpected results from implementing DNSSEC.

---

<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:** [December 24, 2018, 7:19pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/13 "2018-12-24T19:19:17Z")

</div>

You may be able to gather some more information on why DNSSEC is causing complications by dumping the cache while tailing the log.

In one screen/terminal, `sudo tail -f /var/log/pihole.log` and in a second terminal trigger the dump with `sudo pkill -USR1 pihole-FTL`.

---

<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:** [December 24, 2018, 7:23pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/14 "2018-12-24T19:23:46Z")

</div>

> [@DanSchaper](#):
>
> `pihole-FTL` is still based on the 2.79 version of `dnsmasq` . There are issues with the DNSSEC implementation that are expected to be resolved when the FTL moves to the 2.8 branch of `dnsmasq` . We anticipate that happening with Pi-hole version 4.2. Until then there is the chance of unexpected results from implementing DNSSEC.

Ok, but strange that there are suddenly problems after month with that option enabled and several hundreds of thousands successful cached queries (with "OK (cached)" in the Query Log). All is working fine and as expected, then at one morning the cache isn't working anymore.

---

<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:** [December 24, 2018, 7:37pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/15 "2018-12-24T19:37:21Z")

</div>

> [@mibere](#):
>
> one morning the cache isn’t working anymore.

When did you upgrade to V4.1.1 / V4.1.1.2? That's when some bug fix changes were made to the embedded dnsmasq 2.79.

---

<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:** [December 24, 2018, 7:54pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/16 "2018-12-24T19:54:28Z")

</div>

Can you try setting your upstream to Quad 9 (filtered, DNSSEC) and enable DNSSEC to check that configuration. I'm able to get cache population with that configuration, and with DNSSEC disabled. I am seeing an upstream issue that causes no response what so ever if DNSSEC is enabled with an upstream that doesn't reply correctly.

---

<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:** [December 24, 2018, 7:57pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/17 "2018-12-24T19:57:04Z")

</div>

> [@jfb](#):
>
> When did you upgrade to V4.1.1 / V4.1.1.2? That’s when some bug fix changes were made to the embedded dnsmasq 2.79.

The oldest entry with "4.1.2" I can find in one of the pihole-FTL.log-files is

> [2018-12-22 14:00:25.238] FTL version: v4.1.2

---

<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:** [December 25, 2018, 12:35pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/18 "2018-12-25T12:35:30Z")

</div>

It seems it has to do with my DNS server, even if I didn't change any configuration on the server.  
I'm using my own DNS server ([dnscrypt.me](http://dnscrypt.me/)) in Pi-hole, so far with enabled DNSSEC option in the Pi-hole webinterface. But for whatever reason, I have to disable that option now to have a cache again.

---

<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:** [December 25, 2018, 1:36pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/19 "2018-12-25T13:36:08Z")

</div>

Do the corresponding queries show up as INSECURE in your dashboard when you enable DNSSEC in the Pi-hole settings?

---

<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:** [December 25, 2018, 2:17pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/20 "2018-12-25T14:17:01Z")

</div>

No, only "OK (forwarded)" - no "SECURE", "INSECURE", "BOGUS".

I'll let it disabled for now, until pihole-FTL is based on dnsmasq 2.8x (released October 2018).

---

<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:** [December 26, 2018, 4:19pm UTC](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437/21 "2018-12-26T16:19:31Z")

</div>

The development branch is using dnsmasq 2.80 if you would like to try that out.

[Next page](https://discourse.pi-hole.net/t/cache-issue-with-v4-1-2/15437.md?page=2)