FPP 8 cannot DNS Resolve short names.

[bloojoop]

In one of my environments I use a dynamic dns server and my controllers are all set to dhcp. I deliver the domain name via dhcp for both the domain name as well as the search suffix. After upgrading to fpp 8, i noticed that short names no longer can be resolved. I tested the with both 8.4.2 as well as 8.3.1 (still need to upgrade that controller).. This works exactly as expected in FPP 7.5 and earlier.

example.
domain name home.lab
controllers named f16.home.lab, f48.home.lab, k8b.home.lab, etc. when trying to resolve f16, f48, or k8b (or any other) the resolution fails. When resolving the fqdn it works as expected. In fpp 7.5, it resolves using the short names with zero issue.

[ghormann]

@bloojoop is your domain end in ".local"?

[bloojoop]

@ghormann , no it does not. It is home.lab. I also posted in the fpp slack channel. I am using dnsmasq for dhcp and dns and have it configured for domain=home.lab. I also added dhcp-option-force=option:domain-search,home.lab. I am noticing when using systemd-networkd and systemd-resolved (which is what fpp uses), it does not accept the domain name from the dhcp server hence the dhcp-option-force. I also figured out tonight that if I modify /etc/nsswitch.conf to remove the resolve [!UNAVAIL=return] it will once again resolve short names. I found this by comparing between 7.5 and 8.4.2...

[ghormann]

This may be resolved in Master. Needs tested

[patdelaney]

@bloojoop Can you please pull in latest and restest?

[bloojoop]

Yes as mentioned on the call will test this upcoming week. Sent from my iPhoneOn Feb 2, 2025, at 9:13 AM, patdelaney ***@***.***> wrote: @bloojoop Can you please pull in latest and restest? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>