I have a service that runs on a server in a big colocation facility. This server is where other servers report to notify up/down. Very basic stuff. The client agent on each remote server has 1 entry to point to - to report to - and the software has no fault tolerance.
What I would like to do is implement Round-Robin DNS to deal with the main internet connection for the monitoring server at the colo. This system has a large connection but should it go offline I get a bunch of false alerts that the agent servers are offline - when they are in fact not - its that the colo line is down or the firewall for that line is down.
If I do 2 entries in DNS the first being the big bandwidth and main firewall the second being the lower bandwidth and the smaller firewall. Then will these tiny packets of "I am online/offline" from the target agents work better? I know this is not optimum but the software doesn't have code for 2 separate entries for the agents to try. The reporting server isn't offline its rock solid(dual sans and 3 VMWare servers - redundant)... But I have a single point of failure in the firewall and the main line. Just want to try to make this a little better should that line or firewall fail.