This morning (after some scheduled maintenance by my ISP) my domain resolved to the IP address of my secondary connection instead of my primary. (I have a multiWAN config)
I've used this multi wan setup with ClarkConnect for a few years now, and have never observed this behaviour of missed Dynamic DNS updates.
It looks like the update after the scheduled maintenance went missing, but was mentioned as a success in syswatch. After reading this post, could this be a related problem?
Would someone be able to reproduce this behaviour?
I have a ClearSDN standard subscription till 2013
This is wat syswatch says
Thu Jan 7 01:59:10 2010 info: system - dynamic DNS updated <- planned maintenance
Thu Jan 7 02:03:49 2010 info: system - dynamic DNS updated <- primary up again
This is the ClearSDN log, pri is primary IP address, sec is secondary IP address
Automatic IP update xxx.poweredbyclear.com pri January 7, 2010 - 9:38 <-manual update by myself using /usr/sbin/dnsupdate
Automatic IP update xxx.poweredbyclear.com pri January 7, 2010 - 9:31 <-manual update by myself on clearsdn
<NO UPDATE AT 2:03> <- primary up again
Automatic IP update xxx.poweredbyclear.com sec January 7, 2010 - 1:58 <- planned maintenance