DHCP and name resolution

Network DHCP
1

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” 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.

2

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.

3

Sorry. “WUI page”?

NVM, I found it.

Thanks!

4

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?

5

Short answer: yes.

6

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.

7

If you added your entry as
<name>, <interface domainname>, <fixed leases IP>
it should work.
Otherwise it is general bug ²’Edit Hosts’ entries are not included in local name space" to be reported to bugzilla.

8

Works today without any changes. Looks like it took a while to propagate or so. Thanks!