[Dnsmasq-discuss] [BUG] Bogus IP address in the syslog messages

[Sergei Zhirikov]

Hi,

On of the DHCP clients in my network believes that is has the same hostname as the machine where dnsmasq-2.52 is running. That by itself is a result of misconfiguration, but the reaction of dnsmasq seems a bit odd. I get the following messages in syslog when that client tries to renew its lease:

2010-02-16 02:32:48 (6D) wafer dnsmasq-dhcp[6517]: DHCPREQUEST(uml0) 172.23.117.63 02:80:5a:24:9f:c1
2010-02-16 02:32:48 (6D) wafer dnsmasq-dhcp[6517]: DHCPACK(uml0) 172.23.117.63 02:80:5a:24:9f:c1 wafer
2010-02-16 02:32:48 (4D) wafer dnsmasq[6517]: not giving name wafer.local.softlights.net to the DHCP lease of 172.23.117.63 because the name exists in /etc/hosts with address 172.23.112.1
2010-02-16 02:32:48 (4D) wafer dnsmasq[6517]: not giving name wafer to the DHCP lease of 172.23.117.63 because the name exists in /etc/hosts with address 172.23.112.1

2010-02-16 07:58:16 (6D) wafer dnsmasq-dhcp[6517]: DHCPREQUEST(uml0) 172.23.117.63 02:80:5a:24:9f:c1
2010-02-16 07:58:16 (6D) wafer dnsmasq-dhcp[6517]: DHCPACK(uml0) 172.23.117.63 02:80:5a:24:9f:c1 wafer
2010-02-16 07:58:16 (4D) wafer dnsmasq[6517]: not giving name wafer.local.softlights.net to the DHCP lease of 172.23.117.63 because the name exists in /etc/hosts with address 216.230.6.8
2010-02-16 07:58:16 (4D) wafer dnsmasq[6517]: not giving name wafer to the DHCP lease of 172.23.117.63 because the name exists in /etc/hosts with address 172.23.112.1

2010-02-16 13:29:59 (6D) wafer dnsmasq-dhcp[6517]: DHCPREQUEST(uml0) 172.23.117.63 02:80:5a:24:9f:c1
2010-02-16 13:29:59 (6D) wafer dnsmasq-dhcp[6517]: DHCPACK(uml0) 172.23.117.63 02:80:5a:24:9f:c1 wafer
2010-02-16 13:29:59 (4D) wafer dnsmasq[6517]: not giving name wafer.local.softlights.net to the DHCP lease of 172.23.117.63 because the name exists in /etc/hosts with address 172.23.112.1
2010-02-16 13:29:59 (4D) wafer dnsmasq[6517]: not giving name wafer to the DHCP lease of 172.23.117.63 because the name exists in /etc/hosts with address 172.23.112.1

2010-02-16 19:02:05 (6D) wafer dnsmasq-dhcp[6517]: DHCPREQUEST(uml0) 172.23.117.63 02:80:5a:24:9f:c1
2010-02-16 19:02:05 (6D) wafer dnsmasq-dhcp[6517]: DHCPACK(uml0) 172.23.117.63 02:80:5a:24:9f:c1 wafer
2010-02-16 19:02:05 (4D) wafer dnsmasq[6517]: not giving name wafer.local.softlights.net to the DHCP lease of 172.23.117.63 because the name exists in /etc/hosts with address 216.230.6.8
2010-02-16 19:02:05 (4D) wafer dnsmasq[6517]: not giving name wafer to the DHCP lease of 172.23.117.63 because the name exists in /etc/hosts with address 172.23.112.1

The messages about not giving the host name are in principle correct. What is odd is that, as you can see, every other time dnsmasq mentions IP address 216.230.6.8, which is totally bogus. There is nothing in the whole network that even remotely resembles that IP address. The content of /etc/hosts is quite trivial:

# hosts
127.0.0.1 localhost
172.23.112.1 wafer.softlights.net wafer

The problem seems to be just cosmetic, but since it is unclear where the bogus IP address comes from, it is possible that there is a more severe problem (like memory corruption) is hiding behind it.

I'm wondering if anyone can reproduce this phenomenon.

--
Kind regards,
Sergei.