Bug 12664

Summary: unbound-dhcp-leases-bridge does not properly handle underscores given by DHCP clients
Product: IPFire Reporter: Peter Müller <peter.mueller>
Component: ---Assignee: Stefan Schantl <stefan.schantl>
Status: CLOSED INSUFFICIENT_DATA QA Contact:
Severity: Balancing    
Priority: - Unknown - CC: adolf.belka, michael.tremer
Version: 2   
Hardware: all   
OS: All   

Description Peter Müller 2021-07-30 09:56:08 UTC 
Reported here: https://community.ipfire.org/t/not-all-local-hosts-resolve/5822/6

To the best of my knowledge, underscores are valid characters for FQDNs (unless they are terminal, I believe). Hence, we should process them when updating the Unbound dataset for a new DHCP client.
Comment 1 Adolf Belka 2021-07-30 10:18:14 UTC 
Underscores are valid for the Domain Name part of the FQDN but they are not valid for the hostname.

See the subroutines validhostname, validdomainname and validfqdn in
general-functions.pl
Comment 2 Michael Tremer 2021-08-05 20:35:28 UTC 
What is the issue being reported here? In what component?
Comment 3 Adolf Belka 2025-02-02 12:17:53 UTC 
There has been no response to this for 3.5 years.

An underscore in the hostname is not valid.

The unbound-leases-bridge code has been significantly changed at the end of 2024.

Based on the above I am closing this bug.
If it is considered to still be valid then it can be re-opened together with the supporting information from the current Core Update.