# DHCP and name resolution **URL:** \ **Category:** DHCP\ **Created:** [29 July 2026 15:46 UTC](https://community.ipfire.org/t/dhcp-and-name-resolution/16029 "2026-07-29T15:46:00Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![drmacro](https://community.ipfire.org/user_avatar/community.ipfire.org/drmacro/32/15503_2.png) [@drmacro](https://community.ipfire.org/u/drmacro)\ **Post date:** [29 July 2026 15:46 UTC](https://community.ipfire.org/t/dhcp-and-name-resolution/16029/1 "2026-07-29T15:46:00Z")
I am currently on core update 203. I don’t know if this started with 203 because I just noticed it. I can’t seem to use names any more to refer to PC’s on my net. I’m pretty sure it was working. I have all my nodes set to fixed leases and names defined for each. I can, for example, “ping [google.com](http://google.com)” which, of course is outside my net, but “ping ” where is on my green network fails. I can ping and ssh with the ip address, no problem. Is my DNS buggered some how? Since I don’t when or why this changed, I’ve no good idea where to start to figure what to fix. ---
**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:** [29 July 2026 15:50 UTC](https://community.ipfire.org/t/dhcp-and-name-resolution/16029/2 "2026-07-29T15:50:09Z")
With CU203 the remarks of the DHCP fixed leases definitions are not used as host name anymore. There are two ways you can get a name - the client sends a name - you define the name/IP association in ‘Edit Hosts’ WUI page. See also discussions, mainly the CU 203 released thread. ---
**Author:** ![drmacro](https://community.ipfire.org/user_avatar/community.ipfire.org/drmacro/32/15503_2.png) [@drmacro](https://community.ipfire.org/u/drmacro)\ **Post date:** [29 July 2026 15:54 UTC](https://community.ipfire.org/t/dhcp-and-name-resolution/16029/3 "2026-07-29T15:54:12Z")
> [@bbitsch](#): > > - ‘Edit Hosts’ WUI page. Sorry. “WUI page”? NVM, I found it. Thanks! ---
**Author:** ![drmacro](https://community.ipfire.org/user_avatar/community.ipfire.org/drmacro/32/15503_2.png) [@drmacro](https://community.ipfire.org/u/drmacro)\ **Post date:** [29 July 2026 16:41 UTC](https://community.ipfire.org/t/dhcp-and-name-resolution/16029/4 "2026-07-29T16:41:12Z")
> [@bbitsch](#): > So, is the correct way to manage the host names for any device that can’t, won’t, or doesn’t send the host name with a DHCP request to manage the ‘Edit Hosts’ WUI page? ---
**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:** [29 July 2026 17:16 UTC](https://community.ipfire.org/t/dhcp-and-name-resolution/16029/5 "2026-07-29T17:16:32Z")
Short answer: yes. ---
**Author:** ![wussel](https://community.ipfire.org/user_avatar/community.ipfire.org/wussel/32/16158_2.png) [@wussel](https://community.ipfire.org/u/wussel)\ **Post date:** [1 August 2026 17:22 UTC](https://community.ipfire.org/t/dhcp-and-name-resolution/16029/6 "2026-08-01T17:22:40Z")
Adding the fixed lease’s hostname to the “Edit Hosts” list did not resolve the issue in my instance. The hostname still does not get resolved (also not after a restart of ipfire). Command host still yields the following result: Host not found: 5(REFUSED) Facing this (and other) DNS issues since Core-Update 203. ---
**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:** [1 August 2026 17:44 UTC](https://community.ipfire.org/t/dhcp-and-name-resolution/16029/7 "2026-08-01T17:44:00Z")
If you added your entry as `, , ` it should work. Otherwise it is general bug ²’Edit Hosts’ entries are not included in local name space" to be reported to bugzilla. ---
**Author:** ![wussel](https://community.ipfire.org/user_avatar/community.ipfire.org/wussel/32/16158_2.png) [@wussel](https://community.ipfire.org/u/wussel)\ **Post date:** [2 August 2026 09:28 UTC](https://community.ipfire.org/t/dhcp-and-name-resolution/16029/8 "2026-08-02T09:28:31Z")
Works today without any changes. Looks like it took a while to propagate or so. Thanks!