NEOSYS DDNS Service

Using NEOSYS DDNS service

The NEOSYS monitoring server at monitor.neosys.com will update NEOSYS DNS server currently zonedit.com if it is requested to do so by NEOSYS installations. NEOSYS installations do that automatically when updating Nagios and can also have a Windows service configured to do it at all times.

Normally this would only be used at NEOSYS installations that have a dynamic ip number ie do not have a static ip number.

This is not required generally at client installations with static ip numbers or NEOSYS win3/win4 installations but it MAY be used in that situation too to provide for automatic change of static DNS for example to cater for:

• migration from old server to new server
• moving to backup servers
• moving back to live servers
• moving between client's own server and NEOSYS hosts on win3/win4.

Care will be needed to ensure that the DDNS service is not running simultaneously on the both old and new servers.

Configuring the ddns server

ddns server in this case means nagios/monitor which will request NEOSYS's real dns server, currently zoneedit, to change dns ip number as and when it changes

You will only get ddns if there is a file in nagios server /tmp folder

XXXXXXXX is hostname whatever is registered as System ID in the NEOSYS System Configuration File

touch /tmp/XXXXXXXX.client
chmod a+rw /tmp/XXXXXXXX.client

Currently You MUST ALSO inform NEOSYS IT to add your hostname to ddns.py because the above is only a temporary configuration and will be lost when the server is rebooted.

To stop zoneedit being updated you must first inform NEOSYS IT to remove the hostname and then remove the tmp file

Nagios based DDNS

This will only work when NEOSYS processes are running on the client server. Nothing extra needs to be done.

NEOSYS processes when running and updating NAGIOS will automatically update cause NAGIOS to update NEOSYS dns server (zoneedit at the moment)

Using Windows service neosysddns

This will work even when NEOSYS processes are not running. This is useful when NEOSYS processes are stopped overnight and when the server is rebooted, for example for Windows Updates, and NEOSYS processes are not configured to run automatically after rebooting

Starting the service on the client server

In NEOSYS maintenance mode

STARTDDNS

Stopping the service on the client server

In NEOSYS maintenance mode

STOPDDNS

Troubleshooting NEOSYS DDNS Service

On nagios/monitor server to see recent ddns updates for a hostname "XXXX" whatever is entered as System ID in System configuration file.

grep DDNS /var/log/syslog|grep XXXX

or older updates

grep DDNS /var/log/syslog-*|grep XXXX

or to watch new ddns updates as they come in

tail -f /var/log/syslog | grep DDNS

or to watch new ddns updates as they come in for xxxxxxxx

tail -f /var/log/syslog | grep DDNS | grep xxxxxxxx

Lines containing ddns.py are the result of NEOSYS Windows service. Lines containing apache2 are the result of nagios updates. e.g as shown below:

Jan 28 00:03:04 monitor apache2: DDNS IP_NO ums <SUCCESS CODE="200" TEXT="XXXX.hosts.neosys.com updated to 82.178.63.35" ZONE="XXXX.hosts.neosys.com">
Jan 28 01:54:26 monitor ddns.py: DDNS IP_NO 4481 "ddns XXXX" No. 11327 was 82.178.63.35 <SUCCESS CODE="200" TEXT="XXXX.hosts.neosys.com updated to 85.154.7.138" ZONE="XXXX.hosts.neosys.com">