Forum Discussion
[MAJOR ISSUE] b20257, b20262 DNS Server service keeps crashing 0x0374
- I now have that build and it does seem to cure the DNS issues. Thanks"
Thomas Lee hi Thomas from what I have seen in the bugged release the issue happened as soon an DNS record was being updated. I suggest that you get in touch with the Server vNext Team. as Elden_Christensen asked for examples where the rolled out fix in b20270 would not work.
Karl-WE THANKS for that comment. I have indeed written to Elden. NO answer, but it is Sunday morning! 🙂
This is a serious bug and it is one that was previously fixed. I kind of need this bug fixed - it breaks everything. And, why did this bug re-occur? Is this a very weird edge case that slipped through the cracks (it happens :0) )?
What is that joke: The problem is DNS, now what was the question?
My workaround is crude and not perfect:
While ($true) {Start-Service -Name DNS; Start-Sleep -Seconds 3}
- there is also a new release if you like.
https://techcommunity.microsoft.com/t5/windows-server-insiders/announcing-windows-server-preview-build-20285/td-p/2083855- Does this release have a fix for DNS crashes?
doctordns If you upgrade to the newest build and still have this issue, could you please provide some crash dumps and help out with reproduction steps? You can use this to capture crash logs https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps
Also, if you turn on page heap using gflags before running the repro that will be great. More information on that here: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/gflags-and-pageheap#:~:text=To%20enable%20standard%20page%20heap%20verification%20for%20one%20process%2C%20use,p%20%2Fenable%20ImageFileName%20%2Ffull.
- b20282 is also stable for me even after running some days. I would suggest to upgrade to b20282 and eventually remove and reinstall all DNS / ADDS one by one so you have at least one running with your fix. once you notice that after the reinstall the issue is gone this might be your stable route for DNS / ADDS again.
- The suggestion to remove then reinstall DNS has worked. Updating to the latest server dod NOT automatically fix the problem. But on one DC, I removed the dns feature and tools. Rebittef, just to be on the safe side, treinstalled DNS. Since all my zones as AD integrated, they all came back intact and after an hour DNS is stable and working as expected. After 2 hours I repeated the remove and reinstall on DC2 and it, too, is now working.
Thanks for the suggestion!
The solution is DNS, what was the problem?? 🙂doctordns i cannot tell the upgrade alone should have worked. in rare cases features and roles may get into inconsistent states as with yours. usually I see this in Server Manager or other RSAT tools, rarely for others. maybe some files were blocked and did not upgrade, or rather registry settings, correctly. I cannot tell. Setup should have had noticed that.
Karl-WE Thanks for that.
I have downloaded the latest ISO and am upgrading one DC now (after moving OPs Master Roles to second DC). Let's see if that cures this issue. I would prefer NOT to have to uninstall DNS and ADDS if I can avoid it, but will do what I can to ensure a working Server.
I'll report shortly on what I find.
SO....
I have updated to the latest Version and the issue persists.
I am unable to find gflags.exe to set the flags. Clues as to where to find this utility?
