# Unbound: changing logging settings has no effect

**URL:** <https://community.ipfire.org/t/unbound-changing-logging-settings-has-no-effect/15926>\
**Category:** DNS\
**Created:** [4 July 2026 12:02 UTC](https://community.ipfire.org/t/unbound-changing-logging-settings-has-no-effect/15926 "2026-07-04T12:02:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![stepe](https://community.ipfire.org/user_avatar/community.ipfire.org/stepe/32/15448_2.png) [@stepe](https://community.ipfire.org/u/stepe)\
**Post date:** [4 July 2026 12:02 UTC](https://community.ipfire.org/t/unbound-changing-logging-settings-has-no-effect/15926/1 "2026-07-04T12:02:26Z")

</div>

Hi.  
I wanted to change the logging behaviour of unbound in order to get rid of “info” messages spamming in /var/log/messages…

First I used a new file in /etc/unbound/local.d/logging.conf  
`server:`  
`verbosity: 0`  
`val-log-level: 0`  
`use-syslog: yes`  
`log-time-ascii: yes`  
`log-queries: no`  
`log-replies: no`  
`log-local-actions: no`  
`log-servfail: yes`

- → sudo /etc/init.d/unbound restart

- → unbound-control get\_option verbosity  
returned 0  
so it seems that the parameter is set correctly.

BUT the /var/log/messages still gets spammed

I then put these params in  
/etc/unbound/unbound.conf

with the same result

Finally I set `use-syslog: no`

but still get the info messages…

Any idea?

Thank You

---

<div class="post-metadata">

**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\
**Post date:** [4 July 2026 12:04 UTC](https://community.ipfire.org/t/unbound-changing-logging-settings-has-no-effect/15926/2 "2026-07-04T12:04:59Z")

</div>

I wouldn’t spend a lot of time trying to do anything with unbound as from CU203 unbound will no longer be used.

unbound has been replaced by knot-resolver in CU203 and that version is currently in the Testing phase.

[https://www.ipfire.org/blog/ipfire-2-29-core-update-203-is-available-for-testing](https://www.ipfire.org/blog/ipfire-2-29-core-update-203-is-available-for-testing)