Looks familiar. One of the guides I read on configuring direct access said to remove the ISATAP dns block. Unless you have a pre-existing ipv6 network, you shouldn't remove the block. If you are not using direct access, something else may be advertising as an ISATAP router. I'd look at one of the workstations ipconfig /all and see what network has the 2002:2308 address. Most likely it will be one of the tunnel adapters.
From: Kramer, Jack [mailto:jack.kra...@ur.msu.edu] Sent: Monday, February 27, 2012 4:30 PM To: NT System Admin Issues Subject: Re: Windows 2008 DC getting AAAA records instead of A records for DNS They're all 2002:2308 addresses. ---- Jack Kramer Manager of Information Technology University Relations, Michigan State University w: 517-884-1231 / c: 248-635-4955 From: Glen Johnson <gjohn...@vhcc.edu<mailto:gjohn...@vhcc.edu>> Reply-To: NT System Admin Issues <ntsysadmin@lyris.sunbelt-software.com<mailto:ntsysadmin@lyris.sunbelt-software.com>> Date: Mon, 27 Feb 2012 21:25:48 +0000 To: NT System Admin Issues <ntsysadmin@lyris.sunbelt-software.com<mailto:ntsysadmin@lyris.sunbelt-software.com>> Subject: RE: Windows 2008 DC getting AAAA records instead of A records for DNS What are the 1st 4 digits in the ipv6 address. If 2002 or 2001, it could be related to what I just went through. We had unblocked the ISATAP dns entry which was allowing our machines to activate ipv6 address via a tunnel adapter. Re-added the ISATAP dns entry, disable, then re-enable the nic and no more ipv6 registrations. From: Kramer, Jack [mailto:jack.kra...@ur.msu.edu] Sent: Monday, February 27, 2012 3:37 PM To: NT System Admin Issues Subject: Windows 2008 DC getting AAAA records instead of A records for DNS Hi all, Having some trouble with my Windows 2008 DCs and my google-fu has failed me. We have a domain with two 2008 (not R2) controllers and two 2003R2 controllers. DHCP is served on this domain with a set of 2008R2 DHCP servers. Unfortunately, this seems to be causing a problem-our AD's DNS now has AAAA records instead of A records for our client machines running Windows 7. Our network doesn't allow IPv6 traffic so this is obviously not a good thing to have happening. The clients all show their IPv4 address as preferred. Is there any way to fix this? I'd be okay with both AAAA and A records showing up in the DNS, but AAAA records only are a problem. ---- Jack Kramer Manager of Information Technology University Relations, Michigan State University w: 517-884-1231 / c: 248-635-4955 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
