Hi Stefan,

just because you asked...

On Thu, Jul 26, 2012 at 11:14:14PM +0200, Stefan Baur wrote:
> Am 26.07.2012 22:45, schrieb Frank:
...
>> - if you *update* dyndns manually (curl, fetch, wget, whatever) every
>>    10m - does  /that/ work?
>>    ... because just using checkip does not give any information
>>    about if or if not the *update* works when periodically executed
>
> I'm not getting what you're trying to prove or disprove with that.  Care  
> to explain?  Fact is, triggering the update by refreshing the DynDNS  
> page in the WebGUI works.

I will try to explain. 
Fist of all: "work" is short for "updates the dyndns as expected".
If you update dyndns manually 
(something like 
wget -O- --no-check-certificate 
https://user:[email protected]/nic/update?...)
and this works even when called periodically, there is a problem
at your side (script/config).

If the dns is *not* updated, it's possible that dyndns works unreliably
as other people in the thread suspected - or just enforcing the mentioned
update rate limits.

>> - does ist still works, if you call /etc/rc.dyndns.update manually ?

Main difference between /etc/rc.dyndns.update and wget -O- ... is 
that rc.dyndns.update uses the system config. 
So: wget working and rc.dyndns.update not would indicate a config error.

> Depends on what you mean with "works".  I can call the script and it  
> doesn't error out, *but*, it does *not* update the IP.  My guess is that  
> it is trying to check whether or not the WAN IP has changed using its  
> local means (comparing the current interface IP with a previously stored  
> value) and *not* using checkip.dyndns.org. 

that could have been found out using tcpdump :)

.. not necessary any longer as I read - but still a nice exercise.

BTW: Have you thought about using an own DynDNS Server?
Bit of a problem: pfsense seems not to support gnudip natively
(which is one of the easier ways to make your own DynDNS).

-- 
Gruss Frank
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to