On Mon, Feb 1, 2010 at 10:21 PM, Simon Kelley <[email protected]> wrote: > Olaf van der Spek wrote: > >> It's a DNS negative response. >> >> I boot the Debian client, it gets an IP via DHCP. >> I connect to it via SecureCRT on Windows. It does a DNS lookup. >> I reboot the Debian client, it releases the IP. >> The SSH client does a reconnect, so it does a DNS lookup. This one fails... >> This failure is cached (I guess) by Windows. >> The Debian clients boots, gets an IP via DHCP. >> The DNS lookup continues to fail (due to the cache) until it times out. >> > > The fix to this is to stop the DHCP client on the Debian machine from > sending DHCPRELEASE when it shuts down. That's a problem/fix for the > DHCP client (dhclient, dhcpcd, etc) not dnsmasq.
Can't dnsmasq ignore the release for DNS purposes? Olaf -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
