Different approach to fix the same problem

Question

Different approach to fix the same problem

Opened this issue 6 years ago · 4 comments

My DS214Play NAS ran into trouble evenry now and then using your nifty script in that it failed resolving local computers in my network. Resolving outside the network was no problem.

You may want to take a look at the solution I provided, it's on stackoverflow:

https://stackoverflow.com/questions/53163225/how-can-i-update-a-non-windows-dns-server-a-records-from-dhcp-on-a-synology-nas

Nevertheless your script gave me the inspiration to work around it :)

Answer 1 · 2019-10-16T00:09:28.000Z

@HHasenack so how would one switch from this solution to yours, if one should want to?

Answer 2 · 2019-10-16T07:05:54.000Z

Hi Basically I disabled/deleted the scripts I downloaded from your github site on my DSM. After that I modified the dhcp-script.sh (which is already there in DSM6+)) script using an external editor through WinSCP. AfaIk the nsupdate command is already available on DSM6+. More details can be found in the answer on stackoverflow. Van: yepyepyep4711 <notifications@github.com> Verzonden: woensdag 16 oktober 2019 02:09 Aan: gclayburg/synology-diskstation-scripts <synology-diskstation-scripts@noreply.github.com> CC: Hans Hasenack <Hans@sg-assetmanagement.nl>; Mention <mention@noreply.github.com> Onderwerp: Re: [gclayburg/synology-diskstation-scripts] Different approach to fix the same problem (#28) @HHasenack <https://github.com/HHasenack> so how would one switch from this solution to yours, if one should want to? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#28?email_source=notifications&email_token=AE5FDWGYN5XHPHIDXJNTZQDQOZLTTA5CNFSM4GDAWTE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBKTIWY#issuecomment-542454875> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5FDWB44MM3SX76WKXHNXLQOZLTTANCNFSM4GDAWTEQ> .

Answer 3 · 2019-11-01T17:27:25.000Z

Hi @HHasenack ,

so I went and deleted the scripts and replaced the existing dhcpd-script.sh with yours, just changing the name of the zone. Sadly, now the zone doesn't update at all. DHCP works fine, but no update in the DNS is triggered. Any ideas?

Edit: it's a DS416play running "DSM 6.2.2-24922 Update 3"

Answer 4 · 2019-11-04T08:18:45.000Z

Maybe revert to the original DHCP script, and only apply my changes ? Add some logging to see if the script gets called at all? Check if you have a matching DSM version with mine (DSM 6+) Vriendelijke groet, Hans Hasenack | Hoofd ontwikkeling [S&G-new-logo---classic---png] www.sg-assetmanagement.nl<http://www.sg-assetmanagement.nl> Bijsterhuizen 1160b | 6546 AS Nijmegen, the Netherlands T +31 (0) 24 – 645 0006 Van: yepyepyep4711 <notifications@github.com> Verzonden: vrijdag 1 november 2019 18:27 Aan: gclayburg/synology-diskstation-scripts <synology-diskstation-scripts@noreply.github.com> CC: Hans Hasenack <Hans@sg-assetmanagement.nl>; Mention <mention@noreply.github.com> Onderwerp: Re: [gclayburg/synology-diskstation-scripts] Different approach to fix the same problem (#28) Hi @HHasenack<https://github.com/HHasenack> , so I went and deleted the scripts and replaced the existing dhcpd-script.sh with yours, just changing the name of the zone. Sadly, now the zone doesn't update at all. DHCP works fine, but no update in the DNS is triggered. Any ideas? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#28?email_source=notifications&email_token=AE5FDWGMIFTDPZP7WWG257TQRRRH7A5CNFSM4GDAWTE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC3TJII#issuecomment-548877473>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AE5FDWFFIEPFISPXFNNV5ITQRRRH7ANCNFSM4GDAWTEQ>.