Good day, all!
Running into a strange issue…Unsure if related, but an update to the SMB service package happened over the weekend to our Diskstation server, and after that, AD is pretty much non-functional. Folks have issues connecting to the server drives, their desktop icons not loading, access cutting in and out etc. This is because the Synology DNS Server app is crashing…
When I go to Package Manager and try to launch the DNS Server, it loads and then crashes, reverting to “manually stopped”. Log Center does not show anything out of the ordinary. When I reboot the server, the DNS app loads and works correctly for 25 mins, and then it crashes, leaving folks with issues and complaints. In the network settings, DNS is set to 127.0.0.1 and the local IP of the server.
I am fairly new to Synology, and specifically their version of AD, so are there any settings that I would need to change to get the DNS app up and running? It’s just strange that it works as it should for 30 mins or so, then borks out…
I appreciate any assistance you all can give a fairly new IT Admin!
EDIT: We have been running Synology DNS and AD on the same server for years with no issue, which is why I am thinking an update killed it
13 Spice ups
Have you already checked the logs for any warnings, errors, or critical things? That is the first thing to start with anyway, unless you hope Synology support will help you.
A radical option would be exporting your current configuration https://community.spiceworks.com/topic/post/10360058 and reinstalling the DSM from scratch. You can use the current version of the DNS or the one that was working.
I appreciate the response! I had the Log Manager open tracking logs…before the DNS Server app crashed, I took a screenshot of what it was saying. Please see attached. Aside from those errors, nothing out of the ordinary happened. Just client devices authenticating and accessing drives.
Again, I am still learning DNS and server management, so I am not sure if those are normal errors. Please let me know what else you may need. I have heard that Synology Support is less than stellar…
Since the DNS application is crashing, I would look through system logs instead of the DNS itself. I believe the errors you have listed are rather typical, mostly reporting incorrect requests and those kinds of things.
How do you feel about backing up your configuration and trying to reinstall just the DNS server, by the way?
Good to know that the errors are mostly typical! We use Synology Hyper Backup on a daily basis to back up our ~60TB of data…my plan was to, as you said, back up the DNS config, and restore the DNS app to the day before it crashed. I will just be restoring the program/app to the previous state, not restoring the data.
Even before this happened, we ordered a Synology Rack Server for redundancy…it’s coming in the next week or two. So, if what I am going to do doesn’t work, worst case, I’ll get a DNS server set up on the RackStation so we can get AD up and running for folks.
I sincerely appreciate your assistance on this! I am looking forward to not having to go to folk’s machines and re-map their network drives…we’ll let GPO take that job back once we are up and running again
As an update to this situation: On Friday evening, I tried to revert to our backups of that app, and it did not work–the same issue of it works for ~30 mins, then quits. I did make an interesting find…when I restart the SMB service, the DNS app immediately pops up while it’s down. When the SMB service comes back online, the DNS app goes away. Seeing as there was an update to the SMB service 4/28 (when our server broke), I am thinking we will just need to wait for Synology to release a new update to fix the broken update.
In the release notes under Known Issues, it suggests if we migrated from a Windows AD, that we may have issues, but it’s always been on the Synology, never migrated from a Windows AD environment.
The chances of getting a fix with the upcoming update are not that high, to be honest, especially if your issue is unique. It might make more sense to reinstall the DSM from scratch using the previous version (that worked). According to my experience, that operation keeps all the data intact.
Synology Knowledge Center offers comprehensive support, providing answers to frequently asked questions, troubleshooting steps, software tutorials, and all the technical documentation you may need.
Hello
Unfortunately, we didn’t get a solution as of yet.
We had a second Synology server that we used as a backup. What I did was restart the old server, then join the new server to the old one using the built in Directory Server app. Both servers need to be Synology running Directory Server for it to work.
Hi
dutchdc
August 17, 2023, 7:04am
11
Hi Guys, this is fixed with smb update on the synology. But I see other problems after KB5028166 from microsoft that stops windows clients talking to the directory server on Samba (KB5029242 will break this on windows servers and trusts to the synology domains are not working anymore). Not sure if this is fixed with the smb update as well. Please update your smb service the domain is up and running again.
soleil0815
August 17, 2023, 12:10pm
12
You must install a newer SMB Package for Synology 7.1 or 7.2
check your DSM Version
Yep, this issue is fixed with the most recent SMB update!
1 Spice up
