I finally set up a dual-stack DNS forwarder and resolver on my subnet. The forwarder is my primary DNS server and forwards to SixXS's resolvers while the other one recurses directly over IPv4 or IPv6. I had an idea about getting the Microsoft site-local preconfigured DNS addresses to work without much hassle. I simply added one of the site-local addresses on each of my resolvers, and then on my IPv6 router--in my case a Linux PC running aiccu--I added routes to them. Snippet of interfaces file from my recursive resolver box (afterwards I made sure my resolver was bound to the new address): Snippet of my aiccu PC interfaces file: Since the router is the default route for the subnet, all clients on the network can reach fec0:0:0:ffff::2 with no further configuration. Note that the router doesn't even need an fec0:0:0:ffff::/64 address as it can find its neighbor over its link local address. My forwarding resolver ( fec0:0:0:ffff::1 ) is in an OpenVZ VE on the aiccu PC, and it's IP and route are added by OpenVZ. After ping-testing the new addresses I took my IPv4 DNS servers out of my Vista configuration and disabled/enabled the connection. ipconfig /all showed that my only DNS servers were fec0:0:0:ffff::1%1, fec0:0:0:ffff::2%1 and fec0:0:0:ffff::3%1. I tried pinging various places by name and found that name resolution works perfectly! Just to be sure, I shut down the OpenVZ forwarder ( fec0:0:0:ffff::1 ) and tried some more pings to different host names, and it still worked off the recursive resolver ( fec0:0:0:ffff::2 ). So now a Microsoft IPv6 client can now use stateless autoconfiguration on my network and find the DNS servers without help.