SOLVED

[Server 20303.1] DNS Service crashes

%3CLINGO-SUB%20id%3D%22lingo-sub-2217071%22%20slang%3D%22en-US%22%3E%5BServer%2020303.1%5D%20DNS%20Service%20crashes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2217071%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20two%20DCs%20that%20run%20DNS%2C%20with%20integrated%20AD%20zones.%20I%20have%20an%20AD%20forest%20built%20on%20a%20domain%20with%20two%20DCs%2C%20and%20a%20child%20domain.%20In%20earlier%20builds%20of%20Windows%20Server%2C%20this%20all%20works%20great.%20However%2C%20it%20looks%20like%20DNS%20now%20crashes%20pretty%20much%20any%20time%20it%20tries%20to%20do%20anything.%26nbsp%3B%20Every%20time%20I%20restart%20DNS%2C%20it%20crashes%20-%20my%20Application%20log%20is%20full%20of%20error%20events%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E-%20%3CEVENT%20xmlns%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%22%3E%0A-%20%3CSYSTEM%3E%0A%20%20%3CPROVIDER%20name%3D%22Application%20Error%22%3E%3C%2FPROVIDER%3E%20%0A%20%20%3CEVENTID%20qualifiers%3D%220%22%3E1000%3C%2FEVENTID%3E%20%0A%20%20%3CVERSION%3E0%3C%2FVERSION%3E%20%0A%20%20%3CLEVEL%3E2%3C%2FLEVEL%3E%20%0A%20%20%3CTASK%3E100%3C%2FTASK%3E%20%0A%20%20%3COPCODE%3E0%3C%2FOPCODE%3E%20%0A%20%20%3CKEYWORDS%3E0x80000000000000%3C%2FKEYWORDS%3E%20%0A%20%20%3CTIMECREATED%20systemtime%3D%222021-03-17T13%3A12%3A13.4750930Z%22%3E%3C%2FTIMECREATED%3E%20%0A%20%20%3CEVENTRECORDID%3E26332%3C%2FEVENTRECORDID%3E%20%0A%20%20%3CCORRELATION%3E%3C%2FCORRELATION%3E%20%0A%20%20%3CEXECUTION%20processid%3D%220%22%20threadid%3D%220%22%3E%3C%2FEXECUTION%3E%20%0A%20%20%3CCHANNEL%3EApplication%3C%2FCHANNEL%3E%20%0A%20%20%3CCOMPUTER%3EDC1.Reskit.Org%3C%2FCOMPUTER%3E%20%0A%20%20%3CSECURITY%3E%3C%2FSECURITY%3E%20%0A%20%20%3C%2FSYSTEM%3E%0A-%20%3CEVENTDATA%3E%0A%20%20%3CDATA%3Edns.exe%3C%2FDATA%3E%20%0A%20%20%3CDATA%3E10.0.20303.1%3C%2FDATA%3E%20%0A%20%20%3CDATA%3E489408ec%3C%2FDATA%3E%20%0A%20%20%3CDATA%3Edns.exe%3C%2FDATA%3E%20%0A%20%20%3CDATA%3E10.0.20303.1%3C%2FDATA%3E%20%0A%20%20%3CDATA%3E489408ec%3C%2FDATA%3E%20%0A%20%20%3CDATA%3Ec0000005%3C%2FDATA%3E%20%0A%20%20%3CDATA%3E000000000007dec9%3C%2FDATA%3E%20%0A%20%20%3CDATA%3E1558%3C%2FDATA%3E%20%0A%20%20%3CDATA%3E01d71b2f22fd4762%3C%2FDATA%3E%20%0A%20%20%3CDATA%3EC%3A%5CWindows%5Csystem32%5Cdns.exe%3C%2FDATA%3E%20%0A%20%20%3CDATA%3EC%3A%5CWindows%5Csystem32%5Cdns.exe%3C%2FDATA%3E%20%0A%20%20%3CDATA%3E126f4ff8-2316-45b7-812a-f65544ce748c%3C%2FDATA%3E%20%0A%20%20%3CDATA%3E%3C%2FDATA%3E%20%0A%20%20%3CDATA%3E%3C%2FDATA%3E%20%0A%20%20%3C%2FEVENTDATA%3E%0A%20%20%3C%2FEVENT%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20had%20this%20issue%20earlier%20but%20it%20want%20away%20with%20later%20builds.%20But%20now%20it%20seems%20back.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20regression%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2217071%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EManagement%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ENetworking%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2221308%22%20slang%3D%22en-US%22%3ERe%3A%20%5BServer%2020303.1%5D%20DNS%20Service%20crashes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2221308%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F931663%22%20target%3D%22_blank%22%3E%40doctordns%3C%2FA%3E%26nbsp%3BCan%20you%20provide%20a%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwin32%2Fwer%2Fcollecting-user-mode-dumps%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ecrash%20dump%3C%2FA%3E%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2222323%22%20slang%3D%22en-US%22%3ERe%3A%20%5BServer%2020303.1%5D%20DNS%20Service%20crashes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2222323%22%20slang%3D%22en-US%22%3EI%20would%20be%20happy%20to.%3CBR%20%2F%3ECan%20you%20provide%20directions%20as%20to%20how%20to%20do%20it%3F%3CBR%20%2F%3E%3CBR%20%2F%3EAlso%2C%20this%20is%20in%20a%20VM%20and%20I%20can%20export%2C%20zip%20and%20upload%20the%20VM%20which%20is%20failing.%20Give%20me%20an%20FTP%20address%20and%20I%20can%20upload%20it%20(it%20is%20kind%20of%20big%20for%20email).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2222343%22%20slang%3D%22en-US%22%3ERe%3A%20%5BServer%2020303.1%5D%20DNS%20Service%20crashes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2222343%22%20slang%3D%22en-US%22%3Ei%20THINK%20i%20have%20figured%20out%20how%20to%20do%20this.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20dropped%20three%20dumps%20into%3A%20%3CA%20href%3D%22https%3A%2F%2Fwww.dropbox.com%2Fsh%2F97j9wyu185aq19c%2FAABgdD2GP_Dhg9R7fulPML0fa%3Fdl%3D0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.dropbox.com%2Fsh%2F97j9wyu185aq19c%2FAABgdD2GP_Dhg9R7fulPML0fa%3Fdl%3D0%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3ELet%20me%20know%20when%20you%20collect%20these%20so%20I%20can%20get%20rid%20of%20the%20dropbox%20copies.%3C%2FLINGO-BODY%3E
Contributor

I have two DCs that run DNS, with integrated AD zones. I have an AD forest built on a domain with two DCs, and a child domain. In earlier builds of Windows Server, this all works great. However, it looks like DNS now crashes pretty much any time it tries to do anything.  Every time I restart DNS, it crashes - my Application log is full of error events:

 

 

 

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Version>0</Version> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2021-03-17T13:12:13.4750930Z" /> 
  <EventRecordID>26332</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="0" ThreadID="0" /> 
  <Channel>Application</Channel> 
  <Computer>DC1.Reskit.Org</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>dns.exe</Data> 
  <Data>10.0.20303.1</Data> 
  <Data>489408ec</Data> 
  <Data>dns.exe</Data> 
  <Data>10.0.20303.1</Data> 
  <Data>489408ec</Data> 
  <Data>c0000005</Data> 
  <Data>000000000007dec9</Data> 
  <Data>1558</Data> 
  <Data>01d71b2f22fd4762</Data> 
  <Data>C:\Windows\system32\dns.exe</Data> 
  <Data>C:\Windows\system32\dns.exe</Data> 
  <Data>126f4ff8-2316-45b7-812a-f65544ce748c</Data> 
  <Data /> 
  <Data /> 
  </EventData>
  </Event>

 

 

I had this issue earlier but it want away with later builds. But now it seems back.

 

A regression?

11 Replies

@doctordns Can you provide a crash dump?

I would be happy to.
Can you provide directions as to how to do it?

Also, this is in a VM and I can export, zip and upload the VM which is failing. Give me an FTP address and I can upload it (it is kind of big for email).
i THINK i have figured out how to do this.

I have dropped three dumps into: https://www.dropbox.com/sh/97j9wyu185aq19c/AABgdD2GP_Dhg9R7fulPML0fa?dl=0

Let me know when you collect these so I can get rid of the dropbox copies.

@doctordns Thank you for providing the windows error report files. Unfortunately these don't have the crash related information that we are looking for. Can you please provide a crash dump. Instructions to collect crash dump can be found here: Collecting User-Mode Dumps - Win32 apps | Microsoft Docs

 

 

@RutujaShirali 

Sorry about that. So I have set the options as requested and attach some more dumps.

 

Thank you for the dumps, we have analyzed and identified the issue. We have checked in a fix and it will be included in the next Windows Server Insiders build. THANK YOU for your feedback and help in chasing down this issue!!

Thanks!
Elden
That is good news. Looking forward to updating and not needing a workaround.

So glad to have been of assistance.
Does 20137 build have this fix??

No it doesn't, the fix will be in the next build.  Thanks!

best response confirmed by Elden Christensen (Microsoft)
Microsoft Verified Best Answer
Solution
I have downloaded the latest ISO and can confirm that upgrading 20303 to 20324 sees the end of the DNS Issue. I have now updated on DC and DNS is now running fine. Thanks for the fix - and now I'm off to update the other DCs! :)
Great news! thank you for the follow-up and confirming the fix addresses your issue