Neil Haws-Jones

solved: modified "rc.dualserver". Removed the "-d" from "Start dualserver:" section. All good now. WAS: Start dualserver: dualserver_start() { ${EXEFILE} -d -i ${INIFILE} -l ${LOGFILE} -s ${STATEFILE} -n ${ICONFILE} sleep 1 getpid if [ -n "$pidnum" ]; then echo "Dual Server started" else echo "Dual Server failed to start" fi } MODIFIED TO: dualserver_start() { ${EXEFILE} -i ${INIFILE} -l ${LOGFILE} -s ${STATEFILE} -n ${ICONFILE} sleep 1 getpid if [ -n "$pidnum" ]; then echo "Dual Server started"...

systemd[1]: Starting Dual DHCP DNS Server... dualserverd[798]: Error: Invalid Argument /opt/dualserver/dualserver.png Starting on a command line works perfectly, however once demonizing, "dualserverd" will not run.

fixed by installing "DualServerInstaller64bitV7.52.exe" Thank you!

Help, I tried installing version 7.5 (64bit) and get errors after trying to start the program. Screen shots attached. 32bit works fine. Neil

and........ "libwinpthread-1.dll" is missing.

I tried installing version 7.5 (64bit) and get errors after trying to start the program. Screen shots attached. 32bit works fine.

Tim, Short answer.... no. There's no way as Dual DHCP DNS (DDD) server does not support TCP requests. Longer answer: Usually client requests come as a UDP packet and most responses fit within the 512bytes limitation. However there are clients that know/assume the responce is going to be larger than 512bytes and use TCP instead (clairvoyant or bad coding?). Note; TCP is used by DDD for zone transfers, just not requests from clients. In my case it was several Firestick's, running NetFlix, where Netflix...

Frank, I saw this in the RFC, but haven't tested....... The router option specifies a list of IP addresses for routers on the client's subnet. Routers SHOULD be listed in order of preference.