Ubus events contain broken hostnames unless a valid hostname is provided by the DHCP client. Android 10 and later is one example of devices which follow "Anonymity Profiles for DHCP Clients"
(https://datatracker.ietf.org/doc/html/rfc7844#section-3.7) and don't provide a hostname.
The bug can be reproduced with ubus subscribe dhcp.
dhcpv4: fix uninitialized hostname in some ubus events
The hostname buffer is uninitialized if the client doesn't provide
DHCPV4_OPT_HOSTNAME. Use hostname from the assignment which is present if
a static lease contains the hostname or if the client provides one, and
the hostname is valid. It's also used in the ubus ipv4leases method.
Ubus events contain broken hostnames unless a valid hostname is provided by the DHCP client. Android 10 and later is one example of devices which follow "Anonymity Profiles for DHCP Clients" (https://datatracker.ietf.org/doc/html/rfc7844#section-3.7) and don't provide a hostname.
The bug can be reproduced with
ubus subscribe dhcp
.