The GP was the only change we made, and I see, and always saw A records. On Wed, Feb 29, 2012 at 10:02 AM, Kramer, Jack <[email protected]>wrote:
> So, after that GP took effect I no longer see AAAA records in my AD > DNS. That's the good part. The bad part is that I also don't see the host A > records. Any ideas? > > ---- > Jack Kramer > Manager of Information Technology > University Relations, Michigan State University > w: 517-884-1231 / c: 248-635-4955 > > From: University Relations <[email protected]> > > Reply-To: NT System Admin Issues <[email protected]> > Date: Tue, 28 Feb 2012 16:22:38 +0000 > > To: NT System Admin Issues <[email protected]> > Subject: Re: Windows 2008 DC getting AAAA records instead of A records > for DNS > > That makes sense—we use routable IPs for all devices here. (It's fun > having gotten in on the ground floor of the Internet.) I'll configure that > group policy for my client OU and see if that resolves the issue. > > ---- > Jack Kramer > Manager of Information Technology > University Relations, Michigan State University > w: 517-884-1231 / c: 248-635-4955 > > From: Justin Thomas <[email protected]> > Reply-To: NT System Admin Issues <[email protected]> > Date: Tue, 28 Feb 2012 08:59:44 -0600 > To: NT System Admin Issues <[email protected]> > Subject: Re: Windows 2008 DC getting AAAA records instead of A records > for DNS > > So your 6to4 tech is kicking in. You're using routable IPv4 addresses, > and 6to4 is creating IPv6 addresses from them. these will register in DNS > as AAAA records unlike Link Local IPs. We've enabled the 6to4 group policy > and set the state to disabled. The three sites where we use routable IPs > internally now behave like all our other sites. > > On Mon, Feb 27, 2012 at 3:29 PM, Kramer, Jack <[email protected]>wrote: > >> 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 <[email protected]> >> Reply-To: NT System Admin Issues <[email protected]> >> Date: Mon, 27 Feb 2012 21:25:48 +0000 >> To: NT System Admin Issues <[email protected]> >> 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:[email protected]<[email protected]>] >> >> *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 [email protected] >> 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 [email protected] >> 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 [email protected] >> with the body: unsubscribe ntsysadmin >> > > > > -- > Probable Contrarian > > > ~ 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 [email protected] > 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 [email protected] > 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 [email protected] > with the body: unsubscribe ntsysadmin > -- Probable Contrarian ~ 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 [email protected] with the body: unsubscribe ntsysadmin
