[pfS-Dev] DynDNS issues

Wed Oct 5 08:40:43 EDT 2011

I wonder if DynDns change their API.

Are you using DynDNS? I am.

Maybe that is the common denominator.

Anyone else doing Dynamic DNS? Is it working for you? What provider?

-Erik

On Oct 5, 2011, at 8:28 AM, Fuchs, Martin wrote:

> Hmmm,
> but it definitively does not.
> I have more cases and systems here where it shows the correct IP in red, but does not update...
> 
> Sep 21 03:30:16 	php: : phpDynDNS: (Unknown Response)
> Sep 21 03:30:16 	php: : phpDynDNS: PAYLOAD: dnserr
> Sep 21 03:30:16 	php: : DynDns: Current Service: dyndns
> Sep 21 03:30:16 	php: : DynDns: DynDns _checkStatus() starting.
> 
> That's what's in the logs then...
> 
> Perhaps it might be useful to "repeat until 'phpDynDNS: (Success) IP Address Changed Successfully!'" ?
> To have a kind of watchdog ?
> 
> Regards,
> 
> Martin
> 
> -----Ursprüngliche Nachricht-----
> Von: dev-bounces at lists.pfsense.org [mailto:dev-bounces at lists.pfsense.org] Im Auftrag von Erik Kristensen
> Gesendet: Mittwoch, 5. Oktober 2011 13:12
> An: pfSense development mailing list
> Betreff: Re: [pfS-Dev] DynDNS issues
> 
> It "should" be doing that automatically, it just doesn't appear that it is for some reason. The red indicates a bad cache or an unknown ip state, IIRC (anyone else want to chime in)
> 
> So it should be attempting to grab the correct and latest IP, cache it, and update the dyndns provider.
> 
> -Erik
> 
> On Oct 5, 2011, at 7:09 AM, Fuchs, Martin wrote:
> 
>> Hi, Erik !
>> 
>> Perhaps it could be useful to add a function that when the cached IP is marked in red the client retries an update of the dyndns-registration ?
>> What do you think ?
>> 
>> Regards,
>> 
>> martin
>> 
>> -----Ursprüngliche Nachricht-----
>> Von: dev-bounces at lists.pfsense.org 
>> [mailto:dev-bounces at lists.pfsense.org] Im Auftrag von Erik Kristensen
>> Gesendet: Mittwoch, 5. Oktober 2011 13:03
>> An: pfSense development mailing list
>> Betreff: Re: [pfS-Dev] DynDNS issues
>> 
>> Martin,
>> 
>> I am seeing an issue but I haven't upgraded to the latest release yet.
>> 
>> The client doesn't seem to be updating properly, my dyndns.org account 
>> almost expired, when I took a look at the pf UI it said my cached IP 
>> (in red) was 0.0.0.0
>> 
>> I originally designed the client, but that was several years ago, so I am not sure to what extent things have been changed.
>> 
>> The client originally would check and update under the following conditions .
>> 
>> - boot time
>> - interface up/down
>> - daily (I think)
>> 
>> I need to update to the latest version first.
>> 
>> -Erik
>> 
>> On Sep 14, 2011, at 5:44 AM, Fuchs, Martin wrote:
>> 
>>> Hi !
>>> 
>>> Does anyone have DynDNS-issues with pfSense 2.0 ?
>>> 
>>> We have strange issues at some systems here.
>>> We use pfSense 2.0 RC3 build 10.Sept 17:10 and the actual snapshot.
>>> 
>>> The DynDNS-IP is NOT updated and pfSense shows this (by displaying 
>>> the cached IP in red) [see below]
>>> 
>>> ---(update did not work)---
>>> Sep 14 03:00:17 php: : phpDynDNS: (Unknown Response) Sep 14 03:00:17
>>> php: : phpDynDNS: PAYLOAD: dnserr Sep 14 03:00:17 php: : DynDns: 
>>> Current Service: dyndns Sep 14 03:00:17 php: : DynDns: DynDns
>>> _checkStatus() starting.
>>> Sep 14 03:00:16 php: : DynDns: DynDns _update() starting.
>>> Sep 14 03:00:16 php: : DynDns debug information: DynDns: cacheIP != 
>>> wan_ip. Updating. Cached IP: 77.190.222.245 WAN IP: 77.190.212.46 Sep
>>> 14 03:00:16 php: : DynDns: Current WAN IP: 77.190.212.46 Cached IP: 77.190.222.245 Sep 14 03:00:16 php: : DynDns debug information: 77.190.212.46 extracted from local system.
>>> ---(end)---
>>> 
>>> When hitting the save-button in the dyndns-config to manually update 
>>> the IP it works ans pfSense shows the IP in green [see below]
>>> 
>>> ---(update did work)---
>>> 
>>> Sep 14 07:56:51 php: /services_dyndns_edit.php: phpDynDNS: updating 
>>> cache file /conf/dyndns_wandyndns'XXXXXXXX.dyndns.org'.cache: 77.190.212.46 Sep 14 07:56:51 php: /services_dyndns_edit.php: DynDns debug information: 77.190.212.46 extracted from local system.
>>> Sep 14 07:56:51 php: /services_dyndns_edit.php: DynDns: Current
>>> Service: dyndns Sep 14 07:56:51 php: /services_dyndns_edit.php: DynDns: DynDns _checkStatus() starting.
>>> Sep 14 07:56:51 php: /services_dyndns_edit.php: DynDns: DynDns _update() starting.
>>> Sep 14 07:56:51 php: /services_dyndns_edit.php: DynDns debug
>>> information: DynDns: cacheIP != wan_ip. Updating. Cached IP: 
>>> 77.190.222.245 WAN IP: 77.190.212.46 Sep 14 07:56:51 php: /services_dyndns_edit.php: DynDns: Current WAN IP: 77.190.212.46 Cached IP: 77.190.222.245 Sep 14 07:56:51 php: /services_dyndns_edit.php: DynDns debug information: 77.190.212.46 extracted from local system.
>>> Sep 14 07:56:51 php: /services_dyndns_edit.php: DynDns: updatedns() 
>>> starting
>>> ---(end)---
>>> 
>>> 
>>> How often is the IP checked ?
>>> Can we perhaps optimize this somehow ?
>>> 
>>> Should pfSense not try to update the dyndns-IP as long until it is properly updated ?
>>> 
>>> Any thoughts ?
>>> 
>>> Regards,
>>> 
>>> Martin
>>> _______________________________________________
>>> Dev mailing list
>>> Dev at lists.pfsense.org
>>> http://lists.pfsense.org/mailman/listinfo/dev
>> 
>> _______________________________________________
>> Dev mailing list
>> Dev at lists.pfsense.org
>> http://lists.pfsense.org/mailman/listinfo/dev
>> 
>> _______________________________________________
>> Dev mailing list
>> Dev at lists.pfsense.org
>> http://lists.pfsense.org/mailman/listinfo/dev
> 
> _______________________________________________
> Dev mailing list
> Dev at lists.pfsense.org
> http://lists.pfsense.org/mailman/listinfo/dev
> 
> _______________________________________________
> Dev mailing list
> Dev at lists.pfsense.org
> http://lists.pfsense.org/mailman/listinfo/dev