Hmmmm, ok. Well, I had updated to snapshot 2-27 a couple weeks ago and when I tried disabling/reenabling the DynDNS service today I got a php "curl_init" error so maybe something was just broken in that build. I updated to the latest snapshot and it fixed the aforementioned error and and did an update with DynDNS when it started up. Thanks for the info, I won't worry about it for another 25 days then. :) Adam
> Date: Tue, 20 Mar 2007 05:16:52 +0100> From: [EMAIL PROTECTED]> To: > [email protected]> Subject: RE: [pfSense-discussion] Forcing a DynDNS > update> > It already does that every 25 days (iirc) even if the IP has not> > changed.> > Holger> > ________________________________> > From: Adam Van > Ornum [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 20, 2007 5:14 AM> To: > [email protected]> Subject: [pfSense-discussion] Forcing a DynDNS > update> > > Hi, I just got an email today about my DynDNS hostname expiring > but I've> been running the pfSense DynDNS client for a while now. I don't > think> my IP address has changed but DynDNS needs to have an update forced > at> least once a month for the account to remain in "active" status. It> > would be nice to have a way to force an update at specific intervals.> > > > ________________________________> > It's tax season, make sure to follow > these few simple tips Check it out!> > <http://articles.moneycentral.msn.com/Taxes/PreparationTips/PreparationT> > ips.aspx?icid=WLMartagline> > _________________________________________________________________ It’s tax season, make sure to follow these few simple tips http://articles.moneycentral.msn.com/Taxes/PreparationTips/PreparationTips.aspx?icid=WLMartagline
