-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 28/01/16 07:00, Stefan Priebe - Profihost AG wrote: > Hi, > > i've a problem where dnsmasq seems to forget the DNS / hostnames. > > Those devices affected are debian wheezy machines running > dhclient. > > Wenn they're freshly booted the .leases entry looks like this: > > /var/lib/misc/dnsmasq.leases:1454145111 0c:c4:7a:3a:3f:d6 > 10.0.20.203 servername * > > After some ours the entry looks like this: > /var/lib/misc/dnsmasq.leases:1454145111 0c:c4:7a:3a:3f:d6 > 10.0.20.203 * * > > The log entry is this one: > > Jan 26 14:30:09 server1031-han dnsmasq-dhcp[7212]: 2047084359 > client provides name: servername Jan 26 14:30:12 server1031-han > dnsmasq-dhcp[7212]: 2047084359 DHCPDISCOVER(bond0.100) > 0c:c4:7a:3a:3f:d6 Jan 26 14:30:12 server1031-han > dnsmasq-dhcp[7212]: 2047084359 tags: server-ok, server_gw, > ipmisuperm_mac, server_mac, bond0.100 Jan 26 14:30:12 > server1031-han dnsmasq-dhcp[7212]: 2047084359 DHCPOFFER(bond0.100) > 10.0.20.203 0c:c4:7a:3a:3f:d6 Jan 26 14:30:12 server1031-han > dnsmasq-dhcp[7212]: 2047084359 requested options: 1:netmask, > 28:broadcast, 2:time-offset, 3:router, Jan 26 14:30:12 > server1031-han dnsmasq-dhcp[7212]: 2047084359 requested options: > 15:domain-name, 6:dns-server, 119:domain-search, Jan 26 14:30:12 > server1031-han dnsmasq-dhcp[7212]: 2047084359 requested options: > 12:hostname, 44:netbios-ns, 47:netbios-scope, Jan 26 14:30:12 > server1031-han dnsmasq-dhcp[7212]: 2047084359 requested options: > 26:mtu, 121:classless-static-route, 42:ntp-server Jan 26 14:30:12 > server1031-han dnsmasq-dhcp[7212]: 2047084359 next server: > 10.0.16.1 Jan 26 14:30:12 server1031-han dnsmasq-dhcp[7212]: > 2047084359 sent size: 1 option: 53 message-type 2 Jan 26 14:30:12 > server1031-han dnsmasq-dhcp[7212]: 2047084359 sent size: 4 option: > 54 server-identifier 10.0.16.1 Jan 26 14:30:12 server1031-han > dnsmasq-dhcp[7212]: 2047084359 sent size: 4 option: 51 lease-time > 259200 Jan 26 14:30:12 server1031-han dnsmasq-dhcp[7212]: > 2047084359 sent size: 4 option: 58 T1 129600 Jan 26 14:30:12 > server1031-han dnsmasq-dhcp[7212]: 2047084359 sent size: 4 option: > 59 T2 226800 Jan 26 14:30:12 server1031-han dnsmasq-dhcp[7212]: > 2047084359 sent size: 4 option: 1 netmask 255.255.240.0 Jan 26 > 14:30:12 server1031-han dnsmasq-dhcp[7212]: 2047084359 sent size: 4 > option: 28 broadcast 10.0.31.255 Jan 26 14:30:12 server1031-han > dnsmasq-dhcp[7212]: 2047084359 sent size: 4 option: 6 dns-server > 10.0.16.1 Jan 26 14:30:12 server1031-han dnsmasq-dhcp[7212]: > 2047084359 sent size: 25 option: 15 domain-name server.XXX Jan 26 > 14:30:12 server1031-han dnsmasq-dhcp[7212]: 2047084359 sent size: 4 > option: 3 router 10.0.16.1 >
The most likely explanation is that something else got or renewed it's DHCP lease and asked for the same name. Does servername appear anywhere else in the leases file? Cheers, Simon. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBCAAGBQJWr0d+AAoJEBXN2mrhkTWiXG8QAKiYV1HsaWezpAqy+GdpMpf+ 3ETMkjDZxaPNCiuo41PneDO/Zjs4foIMavC1IMTg4rgR2bf54JGPiu9nxkuJ4oEi wsAg9GVe/F/BxOx4WtWup+KicfMD2ed6jZjipwEyiqFpBYEt1cCC2GXxACBuaAJF 9/la89DEVWvnXpFuftygGetbwAY/dQPRgSscQc0wlkhzry2oKFzSCPrJ9R0juKLH 7v0wUnBfVY9tZkEnqaqDMkPLYHbNFIzk3RUuK7geVLIpe8LgVmvG5GNb89fQnBh4 6A01/aZ2jR/gYff/PPZhfrTPwdVELAEA2gSrNhGtLwuVFWyxdkBwayn3j+ccKYng sbt6RAUowhwHtxuARKrNVDs2EIq0oRO31C0vgTfDc11l7LRe/B0PcluCtdPAyh0M Cb5tcy4YRWPDLBFqsK9iXFP3c1yVsu3AJhpOyMTUx3ntPG6Cjoc7IyzXPwEDsl5d oe+JMRvyJdZBecATdv6KsKvWvsVF5bSaTNlJmvbXCGJr+GjFanZ4w8v8VYLTrMZa 1t7o0CWkSepYEI2zOJIo3SpLmmKC0LcELXGrhFNAm5qZe509RKTFroNb2E6R++LU lHHymPsUFteFVhuZXTrAfujFX6QkF85j+scEtP+OaCzlx5jgKblFdAZ72F2o8VH8 HWWiyh2Tqp57o43OM8+i =xycs -----END PGP SIGNATURE----- _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
