The AAAA record for this DC was not found "Rune Flo" <rune.flo[ at ]ri.reslab.no> 12/18/2008 2:11:17 PM A new Windows Server 2008 DC was added to the domain. When compared [in DNS] to other Windows Server 2008 [member] nodes, this DC's IPv6 Host (AAAA) record is missing in DNS. The IPv6 Host (AAAA) record with name "(same as parent folder)" is present though. All IPv4 records are present including the host Host (A) record. The DC is configured with static IPv4 addresses, IPv6 with automatic configuration only [like member servers]. When running "dcdiag /test:dns" on the DC, the output lists several warnings: "Warning: Missing AAAA record at DNS server <IPv4 address>: <FQDN>" This is also the only [W2K8] node replying with IPv4 address when pinging at it. We plan to introduce the first Exchange 2007/SP1 into the org [on W2K8], and was worried about DC's IPv6 name resolution. Has anybody else seeing this? /Rune Flo.

Re: The AAAA record for this DC was not found "Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname[ at ]hotmail.com> 12/18/2008 2:27:13 PM In news:e%23pNAqRYJHA.5272[ at ]TK2MSFTNGP04.phx.gbl, Rune Flo <rune.flo[ at ]ri.reslab.no> requesting assistance, typed the following: [Quoted Text] > A new Windows Server 2008 DC was added to the domain. When compared > [in DNS] to other Windows Server 2008 [member] nodes, this DC's IPv6 > Host (AAAA) record is missing in DNS. The IPv6 Host (AAAA) record > with name "(same as parent folder)" is present though. All IPv4 > records are present including the host Host (A) record. The DC is > configured with static IPv4 addresses, IPv6 with automatic > configuration only [like member servers]. > When running "dcdiag /test:dns" on the DC, the output lists several > warnings: > > "Warning: > Missing AAAA record at DNS server <IPv4 address>: > <FQDN>" > > This is also the only [W2K8] node replying with IPv4 address when > pinging at it. > > We plan to introduce the first Exchange 2007/SP1 into the org [on > W2K8], and was worried about DC's IPv6 name resolution. > > Has anybody else seeing this? > > /Rune Flo. Are all your machines in your infrastructure set to use IPv6? Since all of my customer networks are not using IPv6, that is including on their routers, whether using Win2008 or not, I've simply disabled IPv6. Does your design require it's use? -- Ace This posting is provided "AS-IS" with no warranties or guarantees and confers no rights. Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT Microsoft Certified Trainer For urgent issues, you may want to contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

Re: The AAAA record for this DC was not found "Rune Flo" <rune.flo[ at ]ri.reslab.no> 12/18/2008 3:23:15 PM All machines will eventually be IPv6 ready in not too distant future 1Q 2009 (Vista,W2K8), so I would let the default config remain using IPv6 as the default protocol on the intranet. I was looking for the reason why a [W2K8] DC register different in DNS [regarding IPv6 Host (AAAA) record] than other [W2K8]member servers with identical (IPv4, IPv6) settings. Thanks for replying. /rune. "Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname[ at ]hotmail.com> wrote in message news:eFktQ1RYJHA.6036[ at ]TK2MSFTNGP05.phx.gbl... [Quoted Text] > In news:e%23pNAqRYJHA.5272[ at ]TK2MSFTNGP04.phx.gbl, > Rune Flo <rune.flo[ at ]ri.reslab.no> requesting assistance, typed the > following: >> A new Windows Server 2008 DC was added to the domain. When compared >> [in DNS] to other Windows Server 2008 [member] nodes, this DC's IPv6 >> Host (AAAA) record is missing in DNS. The IPv6 Host (AAAA) record >> with name "(same as parent folder)" is present though. All IPv4 >> records are present including the host Host (A) record. The DC is >> configured with static IPv4 addresses, IPv6 with automatic >> configuration only [like member servers]. >> When running "dcdiag /test:dns" on the DC, the output lists several >> warnings: >> >> "Warning: >> Missing AAAA record at DNS server <IPv4 address>: >> <FQDN>" >> >> This is also the only [W2K8] node replying with IPv4 address when >> pinging at it. >> >> We plan to introduce the first Exchange 2007/SP1 into the org [on >> W2K8], and was worried about DC's IPv6 name resolution. >> >> Has anybody else seeing this? >> >> /Rune Flo. > > > Are all your machines in your infrastructure set to use IPv6? Since all of > my customer networks are not using IPv6, that is including on their > routers, whether using Win2008 or not, I've simply disabled IPv6. > > Does your design require it's use? > > -- > Ace > > This posting is provided "AS-IS" with no warranties or guarantees and > confers no rights. > > Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT > Microsoft Certified Trainer > > For urgent issues, you may want to contact Microsoft PSS directly. > Please check http://support.microsoft.com for regional support phone > numbers.

Re: The AAAA record for this DC was not found "Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname[ at ]hotmail.com> 12/24/2008 12:05:03 AM In news:O9cAPSSYJHA.6036[ at ]TK2MSFTNGP05.phx.gbl, Rune Flo <rune.flo[ at ]ri.reslab.no> requesting assistance, typed the following: [Quoted Text] > All machines will eventually be IPv6 ready in not too distant future > 1Q 2009 (Vista,W2K8), so I would let the default config remain using > IPv6 as the default protocol on the intranet. I was looking for the > reason why a [W2K8] DC register different in DNS [regarding IPv6 Host > (AAAA) record] than other [W2K8]member servers with identical (IPv4, > IPv6) settings. > Thanks for replying. > > /rune. Hello Rune, Ok, so you are moving towards IP6, no problem. What is DNS running on, 2003 or 2008? Do all the respective machines in play (DCs, DNS - assuming the same) have IPv6 installed? The "(same as parent)" name was registered by the Netlogon service, not by the adapter. Therefore we need to take a look at the adapter's settings. Assuming that IP6 is on all machines, as well as the IPv6 IP address configuration was also set in IPv6 properties, and 'register this connection' (which is independent of the netlogon service regsitering the 'same as parent' hostname), is set in the IPv6 properties, I would assume the machine will register. The following link gives a little overview of resolution with IP4 vs IP6: Configuring DNS for IPv6/IPv4 Coexistence http://technet.microsoft.com/en-us/library/cc738372.aspx http://blogs.techrepublic.com.com/networking/?p=530 Also, keep in mind, Windows does not update the reverse zone (look under "How do I configure IPv6 reverse lookups for the DNS Server service in Windows Server 2003?"). However, they should for forward zones. http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx Ace