Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

these scripts do not work in synology active directory / DSM7 #41

Open
TingYsf opened this issue May 4, 2022 · 3 comments
Open

these scripts do not work in synology active directory / DSM7 #41

TingYsf opened this issue May 4, 2022 · 3 comments

Comments

@TingYsf
Copy link

TingYsf commented May 4, 2022

Thank you all very much for these scripts.

I am running AD in synology DSM7, same issue with DHCP not talking to DNS, and I tried this script but does not work.

I remember when I was using DSM6, I used a script and follow the instruction from following link, but now I am using DSM7, somehow I can not find synology's script dhcpd-script.sh under /usr/share/dhcpd/, this folder is no longer there.

Here was old link talking about a new script for DHCP and DNS at AD condition:
https://stackoverflow.com/questions/53163225/how-can-i-update-a-non-windows-dns-server-a-records-from-dhcp-on-a-synology-nas

Wondering anybody have some good ideas?

@nikolarun
Copy link

Hi, I have a similar issue , running AD in DSM7 with pfsense ( the pfsense is doing the DHCP and assigns the DNS of the pfsense as primary and DS as a 2nd one). My DNS logs are full of "client @0x7f2734048e80 192.168.1.162#53566: update 'thevilla.local/IN' denied"
Have you found a solution to this by any chance ?

@gclayburg
Copy link
Owner

These scripts haven't been modified in quite a while. It works for me, but I am only using DSM6. I don't know if it works with DSM7 , AD , or pfsense. Are these scripts still needed with DSM7? You would think at some point this kind of functionality would just get bundled into DSM.

@dougmeek
Copy link

dougmeek commented Nov 6, 2024

@gclayburg, unfortunately, yes, these are still required. I've had to make a couple changes to the code to get it to work with DSM 7, but I think you already have PRs open for those specific issues, going back to 2021.

Speculation: Synology does not seem to have an appetite to create or improve functionality right now. They appear to have put the bean counters in charge and are trying to maximize profits at the expense of users and user experience. (see the 7.2.2 codec removal as an example)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants