I also had many problems and since I use noip now, the problems have gone... It's still the case that dyndns updates sometimes work and sometimes not :-(
Am 25.07.2012 um 18:38 schrieb "RB" <[email protected]>: > On Wed, Jul 25, 2012 at 10:32 AM, Stefan Baur > <[email protected]> wrote: >> Okay, indeed it says so there (and I've updated my crontab accordingly). >> Thanks for pointing that out. > > Not a problem, the problem you outline is of interest to me because I > even see DDNS update issues having a public IP on my WAN; the trigger > doesn't seem to work very well whereas a cron job does tend to. > >> However, repeatedly firing off >> >> fetch -q -o - http://checkip.dyndns.org | sed 's/^.*Current IP Address: >> \(.*\)<\/body>.*$/\1/' >> within the same minute doesn't error out, so it doesn't look like a limit >> that's enforced by dyndns. > > My only guess is that they're enforcing by trend rather than burst. > Regardless, I'll be interested to know your outcome. > _______________________________________________ > List mailing list > [email protected] > http://lists.pfsense.org/mailman/listinfo/list > _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
