Wifi – How to automate DNS server reconfiguration for TCP/IPv4 and TCP/IPv6 in Windows 7

Based on my Googling, here is what I've found:

Both TCP\IP Filtering and the Windows Firewall up to Windows XP were bound to a specific NIC. Regardless of what type of network the computer was connected to, the filtering and firewall were either on or off. This is effective, but not intelligent.

In Vista, 7, and W2K8 the firewall is bound to a specific network profile, not to a NIC. So now it's possible to have different firewall rules and conditions applied to every network adapter or to specific network adapters based on the type of network the computer is connected to. For instance, You can allow incoming HTTP connections to your wireless NIC when you're connected to a private network, but not when you're connected to a public network. You can allow incoming FTP connections to your ethernet NIC when you're connected to a public network but not when you're connected to a private network. Etc., etc. Much more intelligent and much more granular control.

Windows Vista and 7 will request AAAA lookups before A lookups if IPv6 is enabled (and the link local address isn't disabled). Windows by default will have a link local address and will therefor use IPv6 if available. Normally this isn't a problem as the AAAA lookup fails and it happily moves along to IPv4. Most applications however, will just skip straight to IPv4.