Name resolution entirely broken on my network since upgrade to 203

Network DNS
1

The summary says it all. I can’t connect by name from any host on my network to any other host. My network consists entirely of Linux machines, Android phones and a networked Brother printer.

 ben  cube  ~  $  ping printer.cooley.road
ping: printer.cooley.road: Name or service not known
 ben  cube  ~  USAGE  $  ping 192.168.1.3
PING 192.168.1.3 (192.168.1.3) 56(84) bytes of data.
64 bytes from 192.168.1.3: icmp_seq=1 ttl=255 time=1.87 ms
64 bytes from 192.168.1.3: icmp_seq=2 ttl=255 time=1.81 ms
64 bytes from 192.168.1.3: icmp_seq=3 ttl=255 time=2.01 ms
^C
--- 192.168.1.3 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.814/1.899/2.012/0.083 ms

I’ve restarted my IPFire host and every other host on the network. Name resolution continues to fail.

Can you suggest any tips on diagnosing this?

2

Try reloading the DHCP configuration via the dhcp.cgi page, as described here:

If you use DHCP fixed leases, the new version uses the hostname provided by the client.
If you were previously using only the "Remark" field for hostname in dhcp.cgi, you will now need to define them under "Hostname" on the hosts.cgi page.

3

Thank you for the prompt response. I hadn’t found the thread you linked to in my forum searches. Applying the recommended actions now…

4

And that worked - with the additional step of forcing each client to request a new IP address via DHCP after disabling, saving, re-enabling and saving the DHCP server on GREEN. (I have no BLUE.)

Thank you!