DNS Masq Warning Help Needed

[James_Area]

Expected Behaviour:

Good morning, please see below. My Pi-Hole server setup has been running flawlessly until the below issue started occurring.

Actual Behaviour:

PI-Hole server is generating constant error message due to DNSMASQ warning issue with local ip address 192.168.1.90. Name exists in /etc/hosts the error message warns me, but I'm unsure of the correct method to fix. Debug token is below. Appreciate any guidance thank you!

Debug Token:

https://tricorder.pi-hole.net/nx33pMtU/

[jfb]

[2022-01-24 10:31:31.883 596M] WARNING in dnsmasq core: not giving name localhost to the DHCP lease of 192.168.1.90 because the name exists in /etc/hosts with address 127.0.0.1

The warnings have always existed in /var/log/pihole.log. A change to Pi-hole made them more visible by also printing them into /var/log/pihole-FTL.log and showing them on the dashboard.

Add dnsmasq warnings to message table

https://pi-hole.net/2021/12/22/pi-hole-ftl-v5-12-web-v5-9-and-core-v5-7-released

Brief documentation for these warning can be found here:

https://docs.pi-hole.net/ftldns/dnsmasq_warn/

If HOSTNAME is known through a HOSTS file or config (see SOURCE ) and the DHCP address ADDRESS does not match the address in the cache ( CACHE_ADDR ), dnsmasq prevents giving the name to a DHCP client. This prevents possible hostname hijacking by malicious devices.

You can assign a different name to that device.

[James_Area]

Thank you JFB for that information that does help. After some more sleuthing it appears 192.168.1.90 on my local network is our Samsung TV in our living room that is hard-wired. Not sure why it would be trying to create a localhost!?! Went ahead and connected it wirelessly and gave it a new IP address and will see if the behavior continues. Not 100% otherwise the best course of action, but thanks again for your help!