Dynamic DNS from dyndns - how to update as ip changes?
-
Thanks for the reply jimp.
Just to close this thread, so you are saying that setup of DynDNS like you mentioned takes care of the IP updates automatically and there is no need to restart the router for this to update? is that what you can confirm 100% ? Because my IP changed and the change was not reflected onto DynDNS.
Regards,
-
For any router I've ever setup on pfSense with DynDNS, it's updated automatically as the IP changed, and I've not had any issues. On 1.2.3 or 2.0 (at least by the time it hit BETA). I've also added a couple DynDNS types to the code and had no problems with them either. Currently I have four entries setup on 2.0, two for dyndns.org, one for namecheap, and one for he.net.
-
Because my IP changed and the change was not reflected onto DynDNS.
Is the IP address of your pfSense monitored interface(s) a private IP address (for example, pfSense is downstream of a modem/router)? If so, the registration isn't updated until 1AM.
What does your system log display around the time of the address change?
-
Thanks for weighing in wallabybob.
This is a production system so I have to wait until the IP changes again to get the logs.
Why 1 A.M. though? can't this be automated?
Pfsense is connected to Rogers Modem which is just a modem and not a router. This is a coax internet connection so no PPPoE authentication or any other authentication needed.
-
Just to dissolve any fears you might have about using 2.0 RC3. The developers have designed their release candidates to be "stable" releases. Yeah they're not full production releases but you will have little to no problems using them. You will also find using 2.0 versions MUCH better than the 1.x versions.
-
I am testing 2.0 already but I already see that it freezes more often. It is drastically different from 1.2.3. Unfortunately even naming conventions changed and features were removed or misplaced. Doesn't make it easy for a production environment at all. E.g. OpenVPN setup has it's authentication naming changed. Opt1 interface doesn't have bridge mode anymore….etc....one has to go and figure all that out and then test it for 6 months till it's worthy of production. Let alone the fact that it's not STABLE release despite whatever the RC designation is. I understand what you are saying but it's not worthy of production yet as it will bring much more headache than it would solve any problems.
-
It has changed, yes, but it's not as bad as you're making it out to be, and most of the changes are fairly well documented around the forum and even in the GUI itself. The doc wiki has a lot of pages on 2.0, and every page in the GUI has a help icon on it "?" that links you to relevant information in the wiki.
It is quite stable for most people. It is worthy of production, and is being used in production in many locations, with much success.
-
This is a production system so I have to wait until the IP changes again to get the logs.
Not so, the DynDns address checking also occurs on startup. pfSense shell command```
clog /var/log/system.log | grep -i dyndns
@torontob: > Why 1 A.M. though? can't this be automated? It is automated (cron job). If your monitored interface has a private IP address then the only available way of discovering if your PUBLIC ip address is to poll (in this case ask someone on the internet). How often should the poll occur? -
i dont think a free DynDNS account will allow overuse of server queries for ip-change checks, so be sure to read their documentation for those limitations; theres a better change their paid accounts will allow you to ping 'em so to speak far more often; and if thats the case, you can just modify the CRON entry to reflect a more frequent execution
-
Why 1 A.M. though? can't this be automated?
It is automated (cron job). If your monitored interface has a private IP address then the only available way of discovering if your PUBLIC ip address is to poll (in this case ask someone on the internet). How often should the poll occur?
Do you know if there's a way to make this run hourly, every half hour? My IP address changes that often sometimes (crappy, crappy ISP, can't do much about that though) and waiting 18 hours for an update is really frustrating.
-
Yeah, why not update right when the IP changes? code wise that should be easy….
-
If pfSense has the IP that changes on it directly, it does update every time the IP changes.
People with problems have their WAN IPs on a private network with something else ahead of it, so it can't directly detect the IP change.
-
Thanks for the clarification Jimp. Now it makes sense.
