# 152 will not update

**URL:** <https://community.ipfire.org/t/152-will-not-update/3945>\
**Category:** DNS\
**Created:** [3 December 2020 21:11 UTC](https://community.ipfire.org/t/152-will-not-update/3945 "2020-12-03T21:11:02Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![pmueller](https://community.ipfire.org/user_avatar/community.ipfire.org/pmueller/32/9019_2.png) [@pmueller](https://community.ipfire.org/u/pmueller)\
**Post date:** [19 December 2020 09:14 UTC](https://community.ipfire.org/t/152-will-not-update/3945/14 "2020-12-19T09:14:37Z")

</div>

Hi,

thank you for reporting back on this.

To be honest, it is rather unsatisfying not to know what happened here. Based on my  
experience, I am tempted to blame Suricata for this DNS issue, since it seems to drop  
UDP DNS traffic sometimes (without logging it!), but I have no evidence for that.

Unfortunately, we have had to downgrade Suricata to 5.x again in Core Update 153 (see  
[this commit](https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=3b8e39553d7295d6aa7cf5545f73f0191622d7f9) and [this thread](https://community.ipfire.org/t/core-153-testing/4005/) for details), so in case  
Suricata 6.x fixed the error you experienced, I am afraid you will observe it again.

As soon as there is a (hot) fix available from Suricata, we will ship it’s latest version,  
since it comes with some important security fixes as well. But 25 % idle CPU load is  
just too much, especially on smaller systems. 😑

Apart from that, I am glad you like IPFire. 🙂

> The wiki isn’t very detailed.

What information were you missing exactly? Or is the navigation through it tricky?

Thanks, and best regards,  
Peter Müller

---

_[View the full topic](https://community.ipfire.org/t/152-will-not-update/3945)._
