dnsmasq and Windows 7
Posted: Thu Feb 05, 2015 9:30 am
Hi,
I recently installed 1.6.2 on a TP-Link TL-WDR3600 and that went very smoothly. However I'm having issues with two Windows 7 Ultimate laptops playing nicely with DHCP via dnsmasq. A couple of odd things going on:
- Web pages, ping, and other tools work fine, but when I do 'nslookup' the utility will append my local domain to anything I try to resolve (google.com, microsoft.com, redhat.com) and not restrict that to just single-name instances. If I use nslookup with a period at the end (e.g., 'google.com.') it works correctly. I read the material about putting a "." in the "append these suffixes in this order" section of the interface configuration, but I'm confused as to why the default behavior has changed (if anyone knows). Not a big deal but my geek mind wants to know
- More annoying is DHCP issues when the machines are rebooted, come out of sleep, or are otherwise attempting to re-establish their connection. For whatever reason, this doesn't seem to be happening properly. The machines will attempt to 'Identify' to the network, I can see them speaking with the server, and then they just give up and claim the standard '169.254.0.0/16' IP. Getting the connection to work again usually involves disabling the wireless card completely, and/or rebooting the computer a couple of times, or restarting dnsmasq on the router.
Relevant information:
- Version 1.6.2 as I mentioned
- Relevant settings in /etc/config/dhcp
-- filterwin2k = 1
-- dhcp-option=252,\000
-- lease time = 24h
-- local domain is defined
-- all other settings are left as default
- I should mention also, I have other devices on the home network (iPhones/iPads, Linux machines, etc) and none of these seem to have any issues with renewing their lease or re-establishing their connections after going off-network for a while.
I can post the full configuration and some log samples if desired later today. Thanks in advance for any info or advice!
I recently installed 1.6.2 on a TP-Link TL-WDR3600 and that went very smoothly. However I'm having issues with two Windows 7 Ultimate laptops playing nicely with DHCP via dnsmasq. A couple of odd things going on:
- Web pages, ping, and other tools work fine, but when I do 'nslookup' the utility will append my local domain to anything I try to resolve (google.com, microsoft.com, redhat.com) and not restrict that to just single-name instances. If I use nslookup with a period at the end (e.g., 'google.com.') it works correctly. I read the material about putting a "." in the "append these suffixes in this order" section of the interface configuration, but I'm confused as to why the default behavior has changed (if anyone knows). Not a big deal but my geek mind wants to know
- More annoying is DHCP issues when the machines are rebooted, come out of sleep, or are otherwise attempting to re-establish their connection. For whatever reason, this doesn't seem to be happening properly. The machines will attempt to 'Identify' to the network, I can see them speaking with the server, and then they just give up and claim the standard '169.254.0.0/16' IP. Getting the connection to work again usually involves disabling the wireless card completely, and/or rebooting the computer a couple of times, or restarting dnsmasq on the router.
Relevant information:
- Version 1.6.2 as I mentioned
- Relevant settings in /etc/config/dhcp
-- filterwin2k = 1
-- dhcp-option=252,\000
-- lease time = 24h
-- local domain is defined
-- all other settings are left as default
- I should mention also, I have other devices on the home network (iPhones/iPads, Linux machines, etc) and none of these seem to have any issues with renewing their lease or re-establishing their connections after going off-network for a while.
I can post the full configuration and some log samples if desired later today. Thanks in advance for any info or advice!