DNS Service Crashing: This can happen due to a number of reasons, however this solution may get ignorance factor on the first step. Lets take a look at the error message first.

Environment: Windows Server 2008 R2

Log Name:      Application
Source:        Application Error
Date:          22.12.2014 10:32:58
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <Removed>
Faulting application name: dns.exe, version: 6.1.7600.16385, time stamp: 0x5bbac638
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x5bbad923
Exception code: 0x80000003
Fault offset: 0x0000000000043578
Faulting process id: 0xe3c
Faulting application start time: 0x024c2c6df29ea187
Faulting application path: C:\Windows\system32\dns.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll

After troubleshooting the issue, we noticed that the Name Server (NS) records were missing from the server. That did not resolve the issue, we also found that the Client has disabled the Root Hints in DNS. Hence, in any circumstances the query did not make it to the Outside world and failed. So, in simple words, the solution was to FIX Name Servers, and Enable Root Hints.

The following two tabs change content below.
Passionate for Latest Gadgets, a Computer geek by Hobby, and luckily Profession too. Started my career in 2005 with IBM, worked with Microsoft later. Back in 2009, started Pledge Technologies (www.pledgetechnologies.com) (parent company to Grishbi). We, at Pledge Technologies, provide IT Consulting to SMBs across US & UK. Specialized in Microsoft Technologies like AD, Exchange, etc., and lot of experience of Office 365 Migration for various clients. Grishbi is a platform where we express what we learned today, and share it with world.
%d bloggers like this: