DNS/DHCP: Improve error visibility and troubleshooting for dnsmasq failures

[Tbaile]

Summary

When dnsmasq fails (e.g., due to misconfiguration such as setting option 42 ntp-server to a non-IP value), users may lose DNS resolution and DHCP functionality. This is not always evident in the current UI, leading to confusion and delayed troubleshooting.

Proposed solution

• Add a card to the home/dashboard displaying DNS & DHCP status, reflecting the state of the dnsmasq service.
• The card should perform periodic status checks (e.g., ping /etc/init.d/dnsmasq status).
• If dnsmasq is down, display a button linking directly to the log page, with a pre-filled search for 'dnsmasq' to facilitate error diagnosis.
• Consider also displaying a warning in the DNS/DHCP section of the UI.

Purpose
This enhances user awareness of critical DNS/DHCP failures and streamlines troubleshooting.

References

• Helpdesk ticket
• Relevant code discussion
• Mattermost discussion

[AmaLuci]

Mockup ready here

I added a new DNS and DHCP card in the Dashboard.
When dnsmasq is down, the card shows the status “Failed” with a red badge, and a “Go to log” button appears.
By clicking the button, the user is redirected to the Log page with logs already filtered for dnsmasq (the term is prefilled in the search input).

This helps users quickly access the relevant logs.
Still, the most valuable improvement would be to also implement notifications that highlight the exact issue.
Users could then retrieve these details directly from the bell icon, making troubleshooting even clearer and faster.

[gsanchietti]

Design approved