I hate it when two things go wrong at once, or I just notice them at once and think they went wrong at once.
The NSLookup issue was because somehow my IPV6 nics had given themselves an entry for dns lookups. That causes the issue I saw with NSLookup according to google. I will look more into why that happened tomorrow. The Exchange errors were because the Transport Service had started before the Netlogon service had started. From: Kennedy, Jim Sent: Wednesday, October 17, 2012 3:46 PM To: NT System Admin Issues Subject: 6 DNS server suddenly down. All my DNS servers just blew up. AD integrated 2008 R2. Single Forest/Domain. Desktops, clients can all resolve internal and internet IP's via these DNS servers without any trouble. The issue seems to be with AD records. My Exchange servers are screaming at me that they can't find GC's, can't find the topology. The DC's are saying they can't register themselves with themselves. NSLookup on the DC comes back with timeouts or 'unknown' on everything they look up, including themselves. I have rebooted a couple of them. ~ 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
