|
I have two systems located at physically separate locations with different ip addresses assigned by comcast (please forgive me if I use the wrong terminology here). On a daily basis, one server starts failing and, when I look at my systems at the dyndns site, the comcast address for it has been set to the comcast address of the other system! Why is this happening? What have I configured incorrectly? How do I fix this? |
|
"On a daily basis, one server starts failing" What does this exactly mean? "when I look at my systems at the dyndns site" You can't look at your systems there, just at your hostnames and what IP address is currently associated with them. The principle is that each of your sites must update only its DynDNS hostname with its IP address information. In your case it seems you have configured a cross update for the hostnames, i.e. site A updates hostname B (and possibly A as well), and site B updates hostname A (and possibly B as well). Only the site knows its current IP address, so can only update the associated DynDNS hostname, not any other. Therefore, you need to correct this in your Update Client, whatever this is. |
