# DNS Broke without reason

**URL:** <https://community.ipfire.org/t/dns-broke-without-reason/15788>\
**Category:** DNS\
**Created:** [16 May 2026 13:49 UTC](https://community.ipfire.org/t/dns-broke-without-reason/15788 "2026-05-16T13:49:39Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![dcaitcn](https://community.ipfire.org/user_avatar/community.ipfire.org/dcaitcn/32/15609_2.png) [@dcaitcn](https://community.ipfire.org/u/dcaitcn)\
**Post date:** [16 May 2026 13:49 UTC](https://community.ipfire.org/t/dns-broke-without-reason/15788/1 "2026-05-16T13:49:39Z")

</div>

Hello,

The DNS system keeps shutting down for no apparent reason.

The server check shows everything is OK.

 ![dbs-verif-ok](https://community.ipfire.org/uploads/default/original/2X/f/f509920d046dd92c12ebd55e11aaf30fc703cc46.png)

I reconfigured the IP address of the RED interface (using the same IP), the “change” took effect, and the DNS is working again!!

Has anyone else had this problem?

Regards.

---

<div class="post-metadata">

**Author:** ![pscar13](https://community.ipfire.org/user_avatar/community.ipfire.org/pscar13/32/16558_2.png) [@pscar13](https://community.ipfire.org/u/pscar13)\
**Post date:** [16 May 2026 14:57 UTC](https://community.ipfire.org/t/dns-broke-without-reason/15788/2 "2026-05-16T14:57:41Z")

</div>

If you have enabled DNS Firewall, check if you have enough memory.

Look in the `/var/log/messages` file for “`Unbound has died`” after “`kernel: Out of memory`”.

See:

> [@Dns-proxy crashes](https://community.ipfire.org/t/dns-proxy-crashes/15764/12):
>
> So at least, in case of an unbound crash after loading, display the warning on the DNS Firewall page: “You have loaded too many lists, unbound has died”

---

<div class="post-metadata">

**Author:** ![dcaitcn](https://community.ipfire.org/user_avatar/community.ipfire.org/dcaitcn/32/15609_2.png) [@dcaitcn](https://community.ipfire.org/u/dcaitcn)\
**Post date:** [16 May 2026 15:18 UTC](https://community.ipfire.org/t/dns-broke-without-reason/15788/3 "2026-05-16T15:18:16Z")

</div>

> [@pscar13](#):
>
> kernel: Out of memory

Hi Phil,  
Thanks for the quick reply.  
So the DNS firewall was enabled, and I only had 4 GB of RAM.  
I’ve disabled it for now (by unchecking everything) and increased the RAM to 8 GB (the advantage of a virtual machine 🙂 )  
I’m now keeping a close eye on whether it’s stable, and if it is, I’ll close this thread.  
Best regards

---

<div class="post-metadata">

**Author:** ![dcaitcn](https://community.ipfire.org/user_avatar/community.ipfire.org/dcaitcn/32/15609_2.png) [@dcaitcn](https://community.ipfire.org/u/dcaitcn)\
**Post date:** [17 May 2026 09:07 UTC](https://community.ipfire.org/t/dns-broke-without-reason/15788/4 "2026-05-17T09:07:35Z")

</div>

Hi

Everything was working fine this morning, so I enabled the DNS firewall by activating the lists,

 ![dns-selection](https://community.ipfire.org/uploads/default/original/2X/9/92ee3081cc5aebf7485a1bf7269943a27c28ae42.png)

and the DNS server crashed a little while later.  
So I increased the RAM to 10 GB.

I’ll see if it holds up.

---

<div class="post-metadata">

**Author:** ![pscar13](https://community.ipfire.org/user_avatar/community.ipfire.org/pscar13/32/16558_2.png) [@pscar13](https://community.ipfire.org/u/pscar13)\
**Post date:** [17 May 2026 09:16 UTC](https://community.ipfire.org/t/dns-broke-without-reason/15788/5 "2026-05-17T09:16:51Z")

</div>

In fact, you should avoid activating lists multiple times because each time you click “Save,” memory consumption increases.  
You should activate all the lists you need only once (and restart); you shouldn’t need more than 8GB of memory.

---

<div class="post-metadata">

**Author:** ![dcaitcn](https://community.ipfire.org/user_avatar/community.ipfire.org/dcaitcn/32/15609_2.png) [@dcaitcn](https://community.ipfire.org/u/dcaitcn)\
**Post date:** [17 May 2026 12:08 UTC](https://community.ipfire.org/t/dns-broke-without-reason/15788/6 "2026-05-17T12:08:03Z")

</div>

That’s exactly what I did, but with 8 GB of RAM.

Apparently, with 10 GB of RAM, it seems to work.

As we say where I’m from, “Je touche du bois” (I’m knocking on wood) 🙂

---

<div class="post-metadata">

**Author:** ![pscar13](https://community.ipfire.org/user_avatar/community.ipfire.org/pscar13/32/16558_2.png) [@pscar13](https://community.ipfire.org/u/pscar13)\
**Post date:** [17 May 2026 12:56 UTC](https://community.ipfire.org/t/dns-broke-without-reason/15788/7 "2026-05-17T12:56:38Z")

</div>

> [@dcaitcn](#):
>
> As we say where I’m from, “Je touche du bois”

I am from the same country as you. 😉

---

<div class="post-metadata">

**Author:** ![dcaitcn](https://community.ipfire.org/user_avatar/community.ipfire.org/dcaitcn/32/15609_2.png) [@dcaitcn](https://community.ipfire.org/u/dcaitcn)\
**Post date:** [18 May 2026 07:25 UTC](https://community.ipfire.org/t/dns-broke-without-reason/15788/8 "2026-05-18T07:25:41Z")

</div>

Hi  
Update on this issue

It seems everything is working now, and 10 GB of RAM is the minimum requirement.

Merci de ton aide et à une prochaine fois peut-être. 🫡

---

<div class="post-metadata">

**Author:** ![bbitsch](https://community.ipfire.org/user_avatar/community.ipfire.org/bbitsch/32/7420_2.png) [@bbitsch](https://community.ipfire.org/u/bbitsch)\
**Post date:** [18 May 2026 08:50 UTC](https://community.ipfire.org/t/dns-broke-without-reason/15788/9 "2026-05-18T08:50:49Z")

</div>

I tried your DNS Firewall config with my VM. Replacing ‘fast\_reload’ with ‘reload\_keep\_cache’ ( similiar function without the memory leak ) I get a RSS memory usage for DNS of 1.54G. This means without the leak 3.5G of free memory would be sufficient (during fast\_reload a copy of the state is needed). A system with RAM of 5GByte-8GByte should be able to run your very big lists.

The memory usage is equal after a restart, which builds the data base from scratch.  
Means in the moment there are only two possible cases

- doing fast\_reload with minimal DNS outtime, but huge memory consumption
- doing reload with some DNS outtime, but no memory overhead

The solution is to repair the memory leak bug of unbound, but I have little hope ( the issue is known for a long time, and I haven’t got an answer from them yet ☹ )

---

<div class="post-metadata">

**Author:** ![dcaitcn](https://community.ipfire.org/user_avatar/community.ipfire.org/dcaitcn/32/15609_2.png) [@dcaitcn](https://community.ipfire.org/u/dcaitcn)\
**Post date:** [18 May 2026 09:11 UTC](https://community.ipfire.org/t/dns-broke-without-reason/15788/10 "2026-05-18T09:11:37Z")

</div>

Thank you for this information.  
So, since my computer is used for work, I won’t make any changes (since it’s working fine), and we’ll wait for a fix, which still seems a long time coming.  
Best regards

---

<div class="post-metadata">

**Author:** ![bbitsch](https://community.ipfire.org/user_avatar/community.ipfire.org/bbitsch/32/7420_2.png) [@bbitsch](https://community.ipfire.org/u/bbitsch)\
**Post date:** [18 May 2026 09:23 UTC](https://community.ipfire.org/t/dns-broke-without-reason/15788/11 "2026-05-18T09:23:13Z")

</div>

See also [High memory consumption: DNS Proxy Server](https://community.ipfire.org/t/high-memory-consumption-dns-proxy-server/15646)
