I am starting the process of IPv6 integration which I know will take many years. However, I have stumbled at one of the firststeps: DNS registration.Whilst Server 2008 registers it's IPv6 the moment it hits a routable IPv6 network, the Vista client (Enterprise)appears tohave the box unticked bydefault. The only thing I have found that will turn it on is byphysicallylogging on to the 400+PCs and manually calling up the interface and ticking the box.I've tried scripts:netsh interface ipv6 set dnsserver "LANNAME" static fda8:628a:96a:ff30:250:56ff:feb5:612b primaryButdoing a "netsh interface ipv6 show dnsservers" shows that registration is now set on the loopback interface?! The LANNAME interface registration is set to none and the IPv6 GUI interface, the register this connections interface in DNS is unticked.Is this a known bug. If not, who should I tell?Anthony Sheehy - .net

Hi, Thank you for posting. To make our issue clear, we need the following detailed information: 1. Whats the script netsh interface ipv6 set dnsserver for? Can you set the DNS address in the Connection GUI and how it works? 2. If possible, please enable DHCP, let the Windows Vista client obtain the IP address (with DNS servers option) and check how it works. 3. What is the loopback interface? If possible, please help me capture a screenshot on it. By the way, how many interfaces are there on the Vista client? 4. Please let us know how to make "register this connections interface in DNS" unselected and capture a screenshot on this. 5. Please run ipconfig/all on the Windows Vista computer and post the report to the thread. If you think there are some other things need to clarify, please also let us know. Capture a screenshot ============== 1) Press the Print Screen key (PrtScn) on your keyboard. 2) Click the "Start" menu, type "mspaint" in the Search Bar and Press Enter. 3) In the Paint program, click the "Edit" menu, click "Paste", click the "File" menu, and click "Save". 4) The "Save As" dialogue box will appear. Type a file name in the "File name:" box, for example: "screenshot". 5) Make sure "JPEG (*.JPG;*.JPEG;*.JPE;*.JFIF)" is selected in the "Save as type" box, click Desktop on the left pane and then click "Save". Please use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the files and share their URL with me. Thanks you for your efforts. Nicholas Li - MSFT

1 The netsh script was simply an attetmpt to set the 'register' flag without having to visit every one of the 300 client machines on site and set it manually via the GUI. When you set the flag via the GUI the behavior is normal. However, the default setting in the GUI for 'Register this interface in DNS' is off. netsh interface ipv6>set dnsserver "WGS LAN" static fda8:628a:96a:ff30::1 primary netsh interface ipv6>show dnsservers Configuration for interface "WGS LAN" Statically Configured DNS Servers: fda8:628a:96a:ff30::1 Register with which suffix: None Configuration for interface "Loopback Pseudo-Interface 1" Statically Configured DNS Servers: fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 Register with which suffix: Primary only Configuration for interface "Local Area Connection* 6" Statically Configured DNS Servers: None Register with which suffix: None2 Enable DHCP is not available as we are running with a Windows Server 2003 DHCP server. We are auto-configuring clients using RA. Cisco have not implemented configuration of DNS with RA on the routers we have.3 Please see the above for the loopback interface. There is only one NIC on the Vista Client.4 In the LAN properties, highlight Internet Protocol Version 6. Click Properties. Click Advanced. Click the DNS tab. The "Register this connection's Address in DNS... TCP/IP Settings5 See below... C:\Windows\system32>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : RMITST06 Primary Dns Suffix . . . . . . . : westminster.org.uk Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : westminster.org.uk org.uk Ethernet adapter WGS LAN: Connection-specific DNS Suffix . : westminster.org.uk Description . . . . . . . . . . . : Intel(R) 82567LM-3 Gigabit Network Connection Physical Address. . . . . . . . . : 00-22-19-1A-D5-56 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : fda8:628a:96a:ff80:40fa:6e6d:4c27:7e17(Preferred) Temporary IPv6 Address. . . . . . : fda8:628a:96a:ff80:9ccc:5227:e085:7f11(Preferred) Link-local IPv6 Address . . . . . : fe80::40fa:6e6d:4c27:7e17%10(Preferred) IPv4 Address. . . . . . . . . . . : 172.17.24.12(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.252.0 Lease Obtained. . . . . . . . . . : 25 February 2009 23:14:10 Lease Expires . . . . . . . . . . : 06 March 2009 17:16:23 Default Gateway . . . . . . . . . : fe80::20f:90ff:fe2a:58bf%10 fe80::21f:caff:feb0:c5ff%10 fe80::211:20ff:fe87:df7f%10 172.17.24.1 DHCP Server . . . . . . . . . . . : 172.17.4.10 DNS Servers . . . . . . . . . . . : fda8:628a:96a:ff30::1 172.17.4.9 172.17.4.19 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Local Area Connection* 6: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : westminster.org.uk Description . . . . . . . . . . . : isatap.westminster.org.uk Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes C:\Windows\system32> Finally, I have noted a different behaviour on clients thatwere upgraded to SP1 from RTM. Almost all our PCs are rebuilt after a Service Pack. The few that remain get updatednaturally through Windows Update. The ones that upgradeddo register their address, but they pick up the wrongauto-configuration address. This I am not worried about because they are in the minority (3 of them.)Thank you for taking the time to look at it. Sorry about the delay.Anthony Sheehy - .net

Bump...Anything?Anthony Sheehy - .net

Okay, I have discovered that if you have an IPv4 DHCP scopeproperties set to register DNS on behalf of the client, you only get A and PTR records registered, no AAAA records. Vista is big enough and bad enough to register its own interfaces with DNS without the help of DHCP. And when it does, it will register the AAAA records in accordance with http://technet.microsoft.com/en-us/library/bb727035.aspxAnthony Sheehy - .net

Why do you use unique local unicast addresses? You like NAT so much? (-: Maybe it's not too late to switch to global unicast.

It is part of a strategy. <joking>You know, one of those things that allow you to get from A to Z without walking straight into the bear's pit and getting your head bitten off (usually by your immediate superior.)</joking>Once the internal network can handle IPv6 and application compatibility has caught up and (the big AND) the UK ISPs actualy start to offer IPv6, moving to global addressing will be a breeze. At present, most of the ISPs in the UK are standing at the edge of the ice, looking down at IPv6 and are thinking "Who's going to go first?" The answer is that they are all penguins and until customers ask they are going to sit there and look at each other! Approaching our ISP (not mentioning their name, though it begins with 'exponential') at a trade show, I've been officially told that I am the only customer to even mention IPv6 to them. If you understand IPv6 you'll know its not that hard to move from one prefix to another, or even have multiple prefixes. I've done 6to4 and really, what's the point? The other application that is not yet up to IPv6 is ISA. And not for NAT, but for web proxy and filtering. ISA just lets IPv6 through and TMG turns IPv6 off altogether. (Note to TMG guys: "Thanks a bundle, now I am going to have to go Linux or third party!") That could be a bit harsh as I have not looked too hard at TMG to see if it can be wangled through... If I do find a way, I'll blog it.As it goes, this problem appears to be fixed as my Vista PCs have, since late last year, self registering their IPv6 addresses with DNS.Anthony Sheehy - MCP, MCITP

Thanks for this informative post. Looks like we all need to bully our ISPs a little. Also the TMG/UAG teams. One question: assuming I don't yet have an enlightened ISP, where is the best place on a single segment LAN to put the prefix so that all the rest of the LAN finds it? I'm thinking I should not use the DHCP server as autoconfigure seems a better idea. Or do I manually configure the NICs on the DC/DNS machines? And then where can I find a list of hostnames / IP addresses? And what shall I replace my TMG / UAG with please? CarolChi