For DNS/DHCP, you can use the existing Nagios plugins from your Nagios server to check that they're DNS-ing and DHCP-ing properly. If your cluster's running on SLES, you should be able to install the Nagios plugins and NRPE on the SLES servers, then monitor that with check_nrpe on the Nagios box. That will let you check mount points, running processes, etc.
Monitoring over a WAN is possible, but is generally not ideal. This is because if the WAN link goes down or blips all checks will fail and you are blind to what is happening in the remote location. You also have increased latency making it less useful for LAN View performance measurements. That being said if you are going this way you probably want to set up dependencies so you don't get flooded with alerts when the WAN link has issues.
The most common way I have seen communication between a monitoring system and its monitored services is to have a site-to-site VPN tunnel. Then communication is no different from the local network. Also, Nagios is often Pull based (although it doesn't have to be). So Nagios contacts the services and servers it monitors, not the other way around.
Lastly, a more ideal solution is to use a distributed monitoring setup, with Nagios one option is described in http://nagios.sourceforge.net/docs/3_0/distributed.html .
Best Answer
You can try build-in
check_ide_smart