Dynamic DNS didn't work as it should
-
I had an IP change at 2:50 AM and Dynamic DNS didn't update. Below are the logs - can anyone tell me why this happened?
Jun 2 02:50:31 php: : pfSense package system has detected an ip change 84.85.86.87 -> … Restarting packages.
Jun 2 02:50:31 check_reload_status: Starting packages
Jun 2 02:50:34 kernel: ovpnc2: link state changed to UP
Jun 2 02:50:34 check_reload_status: rc.newwanip starting ovpnc2
Jun 2 02:50:40 php: : rc.newwanip: Informational is starting ovpns1.
Jun 2 02:50:40 php: : rc.newwanip: on (IP address: 10.10.60.1) (interface: opt2) (real interface: ovpns1).
Jun 2 02:50:40 php: : rc.newwanip: Informational is starting ovpns3.
Jun 2 02:50:40 php: : rc.newwanip: on (IP address: 172.24.24.1) (interface: opt4) (real interface: ovpns3).
Jun 2 02:50:40 apinger: Exiting on signal 15.
Jun 2 02:50:40 php: : rc.newwanip: Informational is starting ovpns4.
Jun 2 02:50:40 php: : rc.newwanip: on (IP address: 10.10.70.1) (interface: opt6) (real interface: ovpns4).
Jun 2 02:50:41 check_reload_status: Reloading filter
Jun 2 02:50:41 apinger: Starting Alarm Pinger, apinger(16573)
Jun 2 02:50:42 php: : Restarting/Starting all packages.
Jun 2 02:50:42 php: : rc.newwanip: Informational is starting ovpnc2.
Jun 2 02:50:42 php: : rc.newwanip: on (IP address: 10.100.90.6) (interface: opt5) (real interface: ovpnc2).
Jun 2 02:50:42 php: : The command '/usr/local/etc/rc.d/darkstat.sh stop' returned exit code '1', the output was 'No matching processes were found'
Jun 2 02:50:42 apinger: Exiting on signal 15.
Jun 2 02:50:43 ntpdate[52603]: adjust time server 24.102.6.62 offset 0.010246 sec
Jun 2 02:50:43 dnsmasq[47430]: reading /etc/resolv.conf
Jun 2 02:50:43 dnsmasq[47430]: using nameserver 8.8.4.4#53
Jun 2 02:50:43 dnsmasq[47430]: using nameserver 8.8.8.8#53
Jun 2 02:50:43 dnsmasq[47430]: using nameserver 192.168.2.1#53
Jun 2 02:50:43 dnsmasq[47430]: ignoring nameserver 127.0.0.1 - local interface
Jun 2 02:50:43 dnsmasq[47430]: ignoring nameserver 127.0.0.1 - local interface
Jun 2 02:50:43 apinger: Starting Alarm Pinger, apinger(19619) -
What version of pfsense?
-
The log is completely useless. There's nothing about dyndns.
-
The log is completely useless. There's nothing about dyndns.
Exactly!
So, where do I check to see what happened? This is pfSense 2.0.2 -
Cool! I can't find any logs for DynDNS in the GUI… (2.2.2)
I would have a look at the log of your DynDNS provider, to get a first hint what happend.
-
Cant comment on 2.0.2, but in 2.2 provided you tick the option Verbose Logging when setting up the dynamic dns, the logging will appear in the system logs.
You'll be looking for services_dynadns_edit.php in the system logs for 2.2 and possibly in earlier versions.
-
-
So this wasn't a provider issue but was a pfSense issue. Things like this make me sad. How on earth isn't there a re-attempt for things like this? Deves common sense please!
-
pfSense issue ?
I tend to say that it's more an issue that can happen when you use an (very) old version.
News versions have often more functionality (and less bugs ;)).
