2.9.0 and dyndns with no-ip
-
I have several domains which they update their ip with dyndns service at no-ip.
Before upgrading to 2.9.0., even with 26.07 everything was working correct.
After updating dyndns does not sync the new ip with the domains.
My wan is pppoe and i have a gateway group between pppoe and 5g connection (dhcp).
When i manualy run
/etc/rc.dyndns.updateEverything updates as it should.
Trying to trigger this with:
/etc/rc.interfaces_wan_configure wanThen nothing renews
Here are the system logs.
It seems that something is wrong. It detects my wireguard ip as wan ip and cannot renew2026-09-08 22:04:12.933242+03:00 php 43840 NOTICE [pfBlockerNG] DNSBL parser daemon started
2026-09-08 22:04:12.928773+03:00 php_pfb 42438 NOTICE [pfBlockerNG] filterlog daemon started
2026-09-08 22:04:12.836693+03:00 php-cgi 35029 "NOTICE [HAProxy] started new pid:47042\n"
2026-09-08 22:04:12.800812+03:00 php-cgi 35029 "NOTICE [HAProxy] reload old pid:78816\n"
2026-09-08 22:04:11.919246+03:00 vnstatd 35284 Error: pidfile "/var/run/vnstat/vnstat.pid" lock failed (Resource temporarily unavailable), exiting.
2026-09-08 22:04:06.181697+03:00 php-fpm 88856 NOTICE The command '/usr/local/etc/rc.d/bandwidthd.sh stop' returned exit code '1', the output was 'No matching processes were found'
2026-09-08 22:04:04.652964+03:00 php-fpm 22816 NOTICE [Gateway Monitoring] killed policy routing states for tier 2 in MultiWan
2026-09-08 22:04:02.171282+03:00 php-fpm 83763 NOTICE Skipping STARTing packages process because previous/another instance is already running
2026-09-08 22:04:01.371335+03:00 snmpd 78368 disk_OS_get_disks: adding device 'nda0' to device list
2026-09-08 22:04:01.368269+03:00 snmpd 78368 disk_OS_get_disks: adding device 'nda1' to device list
2026-09-08 22:04:00.639109+03:00 check_reload_status 569 Reloading filter
2026-09-08 22:04:00.638990+03:00 check_reload_status 569 Starting packages
2026-09-08 22:04:00.638836+03:00 php-fpm 55081 NOTICE pfSense package system has detected an IP change or dynamic WAN reconnection - 192.168.150.1 -> 192.168.150.1 - Restarting packages.
2026-09-08 22:03:58.939234+03:00 vnstatd 73949 Monitoring (31): tun_wg0 (1000 Mbit) pppoe0 (1000 Mbit) pfsync0 (1000 Mbit) pflog0 (1000 Mbit) ovpns1 (1000 Mbit) ovpnc2 (1000 Mbit) ix3 (10000 Mbit) ix2 (10000 Mbit) ix1.20 (10000 Mbit) ix1.15 (10000 Mbit) ix1 (10000 Mbit) ix0.99 (10000 Mbit) ix0.88 (10000 Mbit) ix0.500 (10000 Mbit) ix0.50 (10000 Mbit) ix0.201 (10000 Mbit) ix0.200 (10000 Mbit) ix0.120 (10000 Mbit) ix0.110 (10000 Mbit) ix0.102 (10000 Mbit) ix0.101 (10000 Mbit) ix0.100 (10000 Mbit) ix0 (10000 Mbit) igc4 (10 Mbit) igc3 (10 Mbit) igc2 (10 Mbit) igc1.835 (1000 Mbit) igc1 (1000 Mbit) igc0.835 (2500 Mbit) igc0 (2500 Mbit) enc0 (1000 Mbit)
2026-09-08 22:03:58.936263+03:00 vnstatd 73949 Data retention: 48 5MinuteHours, 4 HourlyDays, 62 DailyDays, 25 MonthlyMonths, -1 YearlyYears, 20 TopDayEntries
2026-09-08 22:03:58.936184+03:00 vnstatd 73949 vnStat daemon 2.13 (pid:73949 uid:0 gid:0, SQLite 3.53.1)
2026-09-08 22:03:58.625744+03:00 vnstatd 69085 SIGTERM received, exiting.
2026-09-08 22:03:55.801778+03:00 php-fpm 55081 NOTICE [Gateway Monitoring] killed policy routing states for tier 2 in MultiWan
2026-09-08 22:03:53.309269+03:00 php-fpm 48650 NOTICE [Gateway Monitoring] killed policy routing states for tier 2 in MultiWan
2026-09-08 22:03:50.832269+03:00 php-fpm 22816 NOTICE [Gateway Monitoring] killed policy routing states for tier 2 in MultiWan
2026-09-08 22:03:48.539006+03:00 kernel - pppoe0: promiscuous mode enabled
2026-09-08 22:03:48.538970+03:00 kernel - ix0.120: promiscuous mode enabled
2026-09-08 22:03:48.538933+03:00 kernel - ix0.110: promiscuous mode enabled
2026-09-08 22:03:48.538898+03:00 kernel - ix0.99: promiscuous mode enabled
2026-09-08 22:03:48.538852+03:00 kernel - ix0: promiscuous mode enabled
2026-09-08 22:03:48.538814+03:00 kernel - pppoe0: bpf_ifnet_promisc: ifpromisc failed (6)
2026-09-08 22:03:48.538775+03:00 kernel - ix0.120: promiscuous mode disabled
2026-09-08 22:03:48.538734+03:00 kernel - ix0: promiscuous mode disabled
2026-09-08 22:03:48.538695+03:00 kernel - ix0.110: promiscuous mode disabled
2026-09-08 22:03:48.538650+03:00 kernel - ix0.99: promiscuous mode disabled
2026-09-08 22:03:48.445094+03:00 vnstatd 55418 Error: pidfile "/var/run/vnstat/vnstat.pid" lock failed (Resource temporarily unavailable), exiting.
2026-09-08 22:03:47.609161+03:00 snmpd 20242 disk_OS_get_disks: adding device 'nda0' to device list
2026-09-08 22:03:47.606075+03:00 snmpd 20242 disk_OS_get_disks: adding device 'nda1' to device list
2026-09-08 22:03:46.860547+03:00 check_reload_status 569 Reloading filter
2026-09-08 22:03:46.860424+03:00 check_reload_status 569 Starting packages
2026-09-08 22:03:46.860286+03:00 php-fpm 83763 NOTICE pfSense package system has detected an IP change or dynamic WAN reconnection - 5.----- -> 2.--------- - Restarting packages.
2026-09-08 22:03:46.018634+03:00 php-fpm 22816 NOTICE Default gateway setting Interface 01_OPTIC82_PPPOE Gateway as default.
2026-09-08 22:03:46.010919+03:00 php-fpm 22816 NOTICE switch default gateway to: 01_OPTIC82_PPPOE
2026-09-08 22:03:44.719654+03:00 kernel - ovpns1: link state changed to UP
2026-09-08 22:03:44.572649+03:00 check_reload_status 569 rc.newwanip starting ovpns1
2026-09-08 22:03:44.548659+03:00 check_reload_status 569 Reloading filter
2026-09-08 22:03:44.317582+03:00 kernel - ovpns1: link state changed to DOWN
2026-09-08 22:03:44.309904+03:00 check_reload_status 569 Reloading filter
2026-09-08 22:03:43.261333+03:00 php-fpm 83763 ERROR [phpDynDNS] (-----t) Could not determine the request IP address (using "wan", "pppoe0"): gateway not online
2026-09-08 22:03:42.260824+03:00 php-fpm 83763 ERROR [phpDynDNS] (-----.net) Could not determine the request IP address (using "wan", "pppoe0"): gateway not online
2026-09-08 22:03:41.260264+03:00 php-fpm 83763 ERROR [phpDynDNS] (----.net) Could not determine the request IP address (using "wan", "pppoe0"): gateway not online
2026-09-08 22:03:39.259706+03:00 php-fpm 83763 ERROR [phpDynDNS] (-----net) Could not determine the request IP address (using "wan", "pppoe0"): gateway not online
2026-09-08 22:03:38.259199+03:00 php-fpm 83763 ERROR [phpDynDNS] (-----.net) Could not determine the request IP address (using "wan", "pppoe0"): gateway not online
2026-09-08 22:03:37.258782+03:00 php-fpm 83763 ERROR [phpDynDNS] (-----et) Could not determine the request IP address (using "wan", "pppoe0"): gateway not online
2026-09-08 22:03:36.258271+03:00 php-fpm 83763 ERROR [phpDynDNS] (-----net) Could not determine the request IP address (using "wan", "pppoe0"): gateway not online
2026-09-08 22:03:35.257821+03:00 php-fpm 83763 ERROR [phpDynDNS] (------net) Could not determine the request IP address (using "wan", "pppoe0"): gateway not online
2026-09-08 22:03:34.257282+03:00 php-fpm 83763 ERROR [phpDynDNS] (--------net) Could not determine the request IP address (using "wan", "pppoe0"): gateway not online
2026-09-08 22:03:33.906287+03:00 php-fpm 83763 NOTICE Default gateway setting as default.
2026-09-08 22:03:33.898923+03:00 php-fpm 83763 NOTICE switch default gateway to: wan2COTE_4GGW
2026-09-08 22:03:30.202876+03:00 php-fpm 83763 NOTICE Default gateway setting Interface 01_OPTIC82_PPPOE Gateway as default.
2026-09-08 22:03:30.195432+03:00 php-fpm 83763 NOTICE switch default gateway to: 01_OPTIC82_PPPOE
2026-09-08 22:03:24.666677+03:00 php-fpm 83763 NOTICE Default gateway setting as default.
2026-09-08 22:03:24.663020+03:00 php-fpm 83763 NOTICE switch default gateway to: wan2COTE_4GGW
2026-09-08 22:03:22.980224+03:00 check_reload_status 569 rc.newwanip starting pppoe0
2026-09-08 22:03:20.775646+03:00 vnstatd 69085 Traffic rate for "pppoe0" higher than set maximum 1000 Mbit (20s->2673868800, r4256542331 t4275946172, 64bit:0), syncing.
2026-09-08 22:03:16.981657+03:00 kernel - pppoe0: link state changed to UP
2026-09-08 22:03:16.579660+03:00 kernel - pppoe0: link state changed to DOWN
2026-09-08 22:03:16.177928+03:00 kernel - pppoe0: link state changed to DOWN
2026-09-08 22:03:16.177659+03:00 kernel - if_pppoe: pppoe0: failed to clear IP address: 49 -
Are you using a gateway group for the dyndns entries? Are they all failing?
-
@stephenw10
No only the wan interface.
Yes they are all falling -
@AlexanderK ~ I used no-ip for many years but as they got more and more expensive and less and less user friendly, I switched to Cloudflare DNS and DDNS-Go Client and they are both free services and work great!
-
@rpsmith with 2.8.1 everything was working perfect
-
I also use no-ip (paid for) service for several sites.. same domain
No issues so far.. Ill try a failover later today and see if it updates.
However we have been working on one of the sites and have been handed a few new DHCP addresses to the WAN and it followed us just fine.
No CLI however.. all from the GUI.
-
@rpsmith said in 2.9.0 and dyndns with no-ip:
they are both free services and work great!
In 2.9.0? I wouldn't have expected this to be an issue with any specific provider.
-
@stephenw10 ~ My comment was only an FYI for people looking for a free and reliable alternative to no-ip's DDNS service.
-
A AlexanderK referenced this topic on
-
I would like to add that I have the same issue and there is another separate thread about it here:
https://forum.netgate.com/topic/201208/after-pppoe-mpd-restart-dyndns-update-error
Privacy Policy · Cookie Policy