Problems with DynDNS
-
You use PPPOE, i use DHCP through another router. May be this is the Problem.
But in the DynDNS Tab the Ip is highlight red if the wan address change. Can be there a Problem with the trigger?
Who can find this out?cheers
??? -
Have anyone the same Probs?
-
pfSense does not monitor the dns it monitors the wan ip.
If you make the router in front of you renew the dhcp lease frequently that will trigger the update process otherwise only once per day it will be triggered. -
Ok i will try this. Thank you.
-
Is it possible to run the update by adding a cron job in the config.xml. I want to update every hour.?
-
Have anyone the same Probs?
Yes, I actually have the same problem, when I go to Dyndns, Edit and Save, the IP gets green again and becomes updated…
otherwise it stays red even when I get new WAN IPs -
@ermal:
pfSense does not monitor the dns it monitors the wan ip.
If you make the router in front of you renew the dhcp lease frequently that will trigger the update process otherwise only once per day it will be triggered.I presume the intended behaviour is that if the IP address of a DHCP or PPP WAN interface changes a dynamic DNS update should be activated.
I presume it is not necessary for the address to change frequently to trigger an update attempt but that "frequently" here was meant to suggest using a short DHCP lease time should trigger the dynamic dns updates more frequently which should make it a bit easier to figure out what is happening. Else how frequent do the address changes need to be?
I have dynamic DNS monitoring my WAN link (which is ppoe) and I can't see any sign that an IP address change on the WAN interface is triggering a dynamic DNS update attempt. Where should I be able to see a sign of a dynDNS update attempt? (Maybe I'm looking in the wrong place.)
The only time I have been able to see a sign of a dynamic DNS update attempt is when I edit and save a DynDNS entry and then I see a number of lines in the system log.
I went looking for the mechanism that is supposed to trigger the dynamic DNS update and it looks as if both DHCP and ppp are intended to invoke:
# /usr/local/sbin/pfSctl -c "interface newip $interface"but pfSctl is an application rather than a script and I don't have its source on hand so I can't presently follow that path any further.
-
There have been multiple people now that have all had this same problem, and they all made the same mistake!
!!!The Checkbox at the top of the dyndns account settings disables (automatic) Dyndns updates!!!
So go uncheck it ;)
(maybe someone should remove this checkbox or highlight the "disable" somehow, it's easy to overlook, i've made the same mistake, one naturally assumes that its an "enable" switch…)
-
!!!The Checkbox at the top of the dyndns account settings disables (automatic) Dyndns updates!!!
. . .
(maybe someone should remove this checkbox or highlight the "disable" somehow, it's easy to overlook, i've made the same mistake, one naturally assumes that its an "enable" switch…)
Apologies, the Disable box on my Dynamic DNS entry was checked. I disabled that disability and the system log reported a Dynamic DNS update. I'll keep an eye on the system to see if it automatically tracks WAN interface IP address changes.
I'd certainly vote for changing the Disable box to an Enable box (initially not enabled) for greater consistency with other services (e.g. DHCP server, NTP, Captive Portal, PPPoE, RIP and others?)
While on the subject of UI consistency I'd be interested to hear why the PPPoE server has both an Off radio button and an Enable check box? At first sight the Enable check box seems sufficient.
-
For what it's worth, on m0n0wall, this is an Enable when checked box.
-
I dont have any disabled checkbox activated and I also didn't change my configuration…
All I did was upgrading from a 2-3month old release to RC1
All I realized... it was working before..I'll give it another try on the weekend and upgrade to the current snapshot...
If I still have the problem I'll post it here.. -
After an update to the todays version everything works fine again…