Dhcp table not updating ip assignments

Forum rules 1) This is a user forum for Synology users to share experience/help out each other: if you need direct assistance from the Synology technical support team, please use the following form:https://myds.synology.com/support/suppo ... lang=enu2) To avoid putting users' Disk Station at risk, please don't paste links to any patches provided by our Support team as we will systematically remove them.

Our Support team will provide the correct patch for your Disk Station model.

Cheers, Tim Good morning, We have a DS414 running DSM 5.0-4493 Update 5 that we bought to run as a small File/DNS/DHCP/etc in a branch office in a Windows 2008 based company.

I need to setup a local DHCP and DNS so that once clients are given an IP address it is automatically registered in DNS.

I logged in to the NAS as "admin" with ssh and ran the following command:source diskstation_dns_Much of the script worked fine, but I got "Permission denied" and "Operation not permitted" errors on many of the tasks in the script.

(See below for the output.) source diskstation_dns_modify.sh-sh: diskstation_dns_modify.sh: /etc/dhcpd/dhcpd-leases.log: Permission denied Backing up DNS files to /var/services/homes/admin/scripts/dns_backups/DNS_Backup_0815.*INFO: Forward master already backed up for today. Regenerating forward master file Regenerating reverse master file 1.168.192.Overwriting with updated files: 1.168.192.in-addr.arpachown: /var/services/homes/admin/scripts/dns_backups/new: Operation not permittedchown: /var/services/homes/admin/scripts/dns_backups/1.168.192.new: Operation not permittedmv: can't rename '/var/services/homes/admin/scripts/dns_backups/new': Permission deniedmv: can't rename '/var/services/homes/admin/scripts/dns_backups/1.168.192.new': Permission deniedchown: /var/packages/DNSServer/target/named/etc/default/db.empty: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/default/db.127: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/default/named.default-zones.conf: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/default/db.local: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/default/db.root: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/default/db.255: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/default: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/default: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/zone/conf: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/zone/master/chris.lan: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/zone/master/1.168.192.in-addr.arpa: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/zone/master: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/zone/master: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/zone/slave: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/zone/slave: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/zone/data/chris.lan: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/zone/data/1.168.192.in-addr.arpa: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/zone/data: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/zone/data: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/zone: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/zone: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/named.conf: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/conf/named.options.conf: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/conf/named.options.system.conf: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/conf/named.conf: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/conf/named.options.default.conf: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/conf/named.options.resolution.conf: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/conf/conf: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/conf/conf: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/conf/conf: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/conf: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/conf: Operation not permittedchown: /var/packages/DNSServer/target/named/etc/key: Permission deniedchown: /var/packages/DNSServer/target/named/etc/localtime: Operation not permittedchown: /var/packages/DNSServer/target/named/etc: Operation not permittedchown: /var/packages/DNSServer/target/named/etc: Operation not permittedchown: /var/packages/DNSServer/target/named/var/run/named/named.pid: Operation not permittedchown: /var/packages/DNSServer/target/named/var/run/named/session.key: Operation not permittedchown: /var/packages/DNSServer/target/named/var/run/named: Operation not permittedchown: /var/packages/DNSServer/target/named/var/run/named: Operation not permittedchown: /var/packages/DNSServer/target/named/var/run: Operation not permittedchown: /var/packages/DNSServer/target/named/var/run: Operation not permittedchown: /var/packages/DNSServer/target/named/var/log/default-log: Operation not permittedchown: /var/packages/DNSServer/target/named/var/log: Operation not permittedchown: /var/packages/DNSServer/target/named/var/log: Operation not permittedchown: /var/packages/DNSServer/target/named/var: Operation not permittedchown: /var/packages/DNSServer/target/named/var: Operation not permittedchown: /var/packages/DNSServer/target/named: Operation not permittedrndc: error: open: /var/packages/DNSServer/target/named/rndc.key: permission deniedrndc: could not load rndc configuration When I ran the script as "root," everything worked fine.

The Dynamic Host Configuration Protocol (DHCP) uses a client/server structure to provide configuration parameters to hosts.

DHCP consists of a protocol for providing host-specific configuration parameters from a DHCP server (or collection of DHCP servers) to a host, and a mechanism to allocate network addresses to a host.$Backup Path/$Reverse Master File.new########################################################################### Ensure the owner/group and modes are set at default# then overwrite the original filesecho "Overwriting with updated files: $Forward Master File $Reverse Master File"chown nobody:nobody $Backup Path/$Forward Master $Backup Path/$Reverse Master File.newchmod 644 $Backup Path/$Forward Master $Backup Path/$Reverse Master File.new#cp -a $Backup Path/$Forward Master $Zone Path/$Forward Master File #cp -a $Backup Path/$Reverse Master $Zone Path/$Reverse Master File mv -f $Backup Path/$Forward Master $Zone Path/$Forward Master File mv -f $Backup Path/$Reverse Master $Zone Path/$Reverse Master File ########################################################################### Reload the server config after modifications $Zone Root Dir/script/reload.shexit 0I updated the script to handle when the DHCP leases log doesn't exist yet because no addresses have been assigned. It appears the historical DHCP leases are stored there.This happens whenever DHCP configuration changes are made. Tim, Thank you so very much for all the effort you put into making this work. I was able to get everything up and running, but when I ran the script in the Task Scheduler as "Admin," it failed.When the DHCP server is loaded, it reads its configuration information from e Directory and stores the information in its cache.As the DHCP server assigns addresses to clients, it updates e Directory, adding IP address objects or modifying their e Directory status information.I had no trouble doing this with BIND, but this half-assed Synology name server refuses to do it.

Tags: , ,