# CU203 static dhcp entries not resolving

**URL:** <https://community.ipfire.org/t/cu203-static-dhcp-entries-not-resolving/15906>\
**Category:** DNS\
**Created:** [22 June 2026 10:51 UTC](https://community.ipfire.org/t/cu203-static-dhcp-entries-not-resolving/15906 "2026-06-22T10:51:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rjackson](https://community.ipfire.org/user_avatar/community.ipfire.org/rjackson/32/15350_2.png) [@rjackson](https://community.ipfire.org/u/rjackson)\
**Post date:** [22 June 2026 10:51 UTC](https://community.ipfire.org/t/cu203-static-dhcp-entries-not-resolving/15906/1 "2026-06-22T10:51:35Z")

</div>

Hi,

I’m new to IPFire so may be missing the obvious or this may be expected behaviour with the new knox resolver.

Dynamically assigned dhcp leases are being resolved by either of host name or host.domain, however, static dhcp entries are not being resolved at all. As a workaround I added the fixed leases to “edit hosts” which works fine.

Richard

---

<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:** [12 July 2026 06:47 UTC](https://community.ipfire.org/t/cu203-static-dhcp-entries-not-resolving/15906/2 "2026-07-12T06:47:36Z")

</div>

Hi @rjackson

Thank you for your reply. I had also noticed that your post had not received a response.

Part of the explanation may be found here:

> [@CU203 Test : dhcp entries not resolving](https://community.ipfire.org/t/cu203-test-dhcp-entries-not-resolving/15940):
>
> I have the same issue of To whom no one replied DHCP hosts are not registered in knot-resolver (static and dynamic). Here is the extract from /var/ipfire/dhcp/dhcpd.conf deny bootp; #default authoritative; ddns-update-style none; option wpad code 252=text; subnet 192.168.20.0 netmask 255.255.255.0 #GREEN { pool { range 192.168.20.203 192.168.20.208; } option subnet-mask 255.255.255.0; option domain-name "pshome"; option routers 192.168.20.1; option domain-name-servers 192.168.20.…

That said, your post doesn’t provide much information, which makes it difficult for others to offer a meaningful answer.

A project like IPFire is complex. The IPFire team is relatively small but very active, and it is not always possible for them to respond to every forum question or every bug report.  
Sometimes a post doesn’t include enough information, as in this case. Sometimes it may include too much, which is often true of my own posts—I readily admit that.  
We all come from different countries, with different cultures, communication styles, and sensitivities. We are all human, and misunderstandings can happen. Using translation tools doesn’t always help either.

Despite that, I keep posting my findings, even when they don’t receive a reply, because I think they may still be useful to other users, like you.

---

<div class="post-metadata">

**Author:** ![rjackson](https://community.ipfire.org/user_avatar/community.ipfire.org/rjackson/32/15350_2.png) [@rjackson](https://community.ipfire.org/u/rjackson)\
**Post date:** [12 July 2026 09:28 UTC](https://community.ipfire.org/t/cu203-static-dhcp-entries-not-resolving/15906/3 "2026-07-12T09:28:56Z")

</div>

@pscar13

Yep, I acknowledge my post lacked detail.

From my perspective I wasn’t looking for support or community help, I was simply reporting an apparent regression.

I fully accept it’s a small team and to the extent I suggested I felt “let down” I would apologise that was not what I intended to convey.