No-IP DDNS Client - Broken in 2.8.1 ?
-
Hi Guys,
I've worked round using Chron and Curl command - but I need to use the Gateway Group ultimately.
I use No-IP to create an always active target for incoming connections on several firewalls with Dual WAN- However - I don't seem to be able to get a cached IP green tick since 2.8.1 ?
Anyone else go this issue ?
-
I've used no-ip ones, the free version. I needed to re login, manually, every month for the account to survive. They send a mail as a reminder ... and if you lost the mail or forgot to do your part, your IP was not registered anymore ...
So, I ave to ask : what account type do you use ?You want to know what is going on. Did you set :
?
And if you did, can you share with us what you saw ?
And be ware : no-ip, as any other DDNS service, can change their offer whenever they want, and it's 'normal' that that won't tell you something changed on their side.
Remember : it's free after all ^^
Their support forums (other users) will mention if this happens, though. -
@Gertjan I use the paid version.
On all my stuff. Its most curious - it just stopped working with 2.8.1 using the GUI -
Using IPv4?
Was is working for you in 2.8.0 or did you come from 2.72?
-
@Jake-Biker said in No-IP DDNS Client - Broken in 2.8.1 ?:
I've worked round using Chron and Curl command
Did you find the script on this forum ?
I found some no-ip ddns issues, many (or more) month ago, it could have been in the 2.7.2 days.The pfSense DDNS script that handles no-ip, and all the others, is here. The thing is, it didn't really change recently.
The verbose logging could surface the issue as if an error would occur while updating.
Example : if to many non needed updates (your WAN IP didn't change) did occur, subsequent updates will be blocked. That's why, on the pfSense side, when a successful update is executed, a time stamp and the updated WAN IP is recorded in a file.
You can find that file in this folder : /cf/conf/ and it starts with dyndns_wan.....82.127.54.109|1757286063where you can see the WAN IP and the timestamp.
As long as your current (pfSense) WAN IP is the same as the one stored in the file, no upgrade will happen. Because it's up to date.This URL is used to determine your WAN IP : Services > Dynamic DNS > Check IP Services
http://checkip.dyndns.org
(click to see the magic happening : your WAN IPv4 should show up in the browser page.) -
@stephenw10 I rebuilt my own DMZ and LAN Firewalls for my lab - went straight to 2.8.1 from the downloadable image.
Curiously enough, I have a NON Lab FW that come from well before two years and that has a NO-IP and shows the IP Cached.
-
@Gertjan I need to try and find those logs!
-
@Gertjan Sorry - its widely known you can Curl into No-IP with various details.
I'm thinking about the logic around the gateway group - I guess the gateway group will just create a single dominant connection based on the set criteria and then the Curl will just respect that IP.Try to get some logs out of this.
-
@Jake-Biker said in No-IP DDNS Client - Broken in 2.8.1 ?:
went straight to 2.8.1 from the downloadable image.
Ok but what version were they running last when it was working?
-
@stephenw10 2.8.0 but upgraded from 2.7.2
UPDATE >
Logs
Dynamic DNS (hostname.ddns.net) There was an error trying to determine the public IP for interface - wan (vtnet0 ).
Which is odd - because its got a DHCP address!
-
OK - yeah this is starting to look like a bug.
2.7.2 ISO and upgrade - works
2.8.1 online build - doesn't work.Log entry as above on the one that doesn't work
-
So 2.8.0 also worked? Interesting.
Do you have gateway monitoring enabled on that WAN? Does that gateway show as online? One change in the behaviour of the dyndns client is that it will no longer update against a WAN shown as down.
-
BINGO !!
Thanks again as ever. My ISP recently changed the behaviour on the fibre accounts. The upstream gateway showed offline - I changed the monitor IP and - all working - thanks so much!!
