I have DynDNS.org set up on my Balance One. It updates sometimes when the Balance One fails over or fails back from primary WAN 1 to mobile WAN 2.
Where I notice this most often is when it doesn’t update DNS when going back to WAN 1 after a failover to WAN 2. DynDNS continues to show the WAN 2 IP for at least several hours, maybe indefinitely.
Having a Dynamic DNS feature on the router is a great idea, provided that it works reliably. If it doesn’t work reliably, it is a booby trap.
I don’t know what triggers the updater on the Balance One, but clearly it is not doing a sufficient job.
This is the only issue I’ve had with the Balance One. Otherwise it has been rock solid and reliable. It is disappointing that the Dynamic DNS update doesn’t work reliably when everything else works so well and much cheaper routers are able to get Dynamic DNS right.
Hi. I’m wondering if this is the same issue as discussed here …
So far as I know, the DDNS updating issue (particularly, following “preferred” WAN when it returns to good health) has not been addressed.
We and our clients generally use no-ip.com and have found it to be nearly 100% reliable when properly updated. However, suppose there is a situation where one has two WANs. WAN 1 has a high capacity and WAN 2 is a “dog” but serves as a back-up. If WAN 1 fails, the DDNS on WAN 2 will be updated but will usually NOT be updated again once WAN 1 (the one with far greater capacity) returns to good health. So, inbound traffic will use the “dog” WAN even though the good one is performing well.
I’ve looked at the firmware release notes and I don’t see where any changes to this behavior have been discussed.
Dynamic DNS update should work for the WAN fail-over from Primary WAN to the backup WAN or recover from backup WAN to the primary WAN (Primary WAN is Active and Backup WAN is in standby) .
Please check the simulation logs below:
Aug 08 10:01:56 DDNS: Domain mypeplink.myftp.info updated successfully for WAN 1
Aug 08 10:01:54 WAN: Mobile Internet standby (10.248.4.201)
Aug 08 10:01:54 WAN: WAN 1 connected (192.168.52.27)
Aug 08 10:01:12 DDNS: Domain mypeplink.myftp.info updated successfully for Mobile Internet
Aug 08 10:01:11 WAN: Mobile Internet connected to Celcom (10.248.4.201)
Aug 08 10:01:11 WAN: WAN 1 disconnected (WAN failed PING test)
Aug 08 10:01:09 DDNS: Domain mypeplink.myftp.info updated successfully for WAN 1
Aug 08 10:01:03 System: Changes applied
Aug 08 09:59:20 DDNS: Domain mypeplink.myftp.info updated successfully for WAN 1
Aug 08 09:59:19 WAN: Mobile Internet standby (10.248.4.201)
Aug 08 09:59:14 System: Changes applied
Aug 08 09:58:18 DDNS: Domain mypeplink.myftp.info updated successfully for WAN 1
Aug 08 09:58:12 System: Changes applied
Aug 08 09:58:08 WAN: Mobile Internet disconnected (Cold standby)
Aug 08 09:58:06 DDNS: Domain mypeplink.myftp.info updated successfully for WAN 1
Aug 08 09:58:04 WAN: WAN 1 connected (192.168.52.27)
Aug 08 09:56:09 DDNS: Domain mypeplink.myftp.info updated successfully for Mobile Internet
Aug 08 09:56:08 WAN: Mobile Internet connected to Celcom (10.247.166.177)
Aug 08 09:55:50 WAN: WAN 1 disconnected (WAN failed PING test)
Aug 08 09:55:46 DDNS: Domain mypeplink.myftp.info updated successfully for WAN 1
Aug 08 09:55:41 System: Changes applied
Aug 08 09:54:38 WAN: Mobile Internet disconnected (Cold standby)
Aug 08 09:54:31 DDNS: Domain mypeplink.myftp.info updated successfully for WAN 1
Aug 08 09:54:29 WAN: WAN 1 connected (192.168.52.27)
Aug 08 09:53:39 DDNS: Domain mypeplink.myftp.info updated successfully for Mobile Internet
Aug 08 09:53:37 WAN: Mobile Internet connected to Celcom (10.247.110.58)
Do you find any logs indicate that the dyndns.org update fail for your device ?
@Rick-DC The shared forum link is more to feature request for all active WAN sharing the same dyndns host/domain name. I think the reported issue by @cover is not related to the link.
But do you find that when DDNS is enabled for multiple WANs that the DDNS message to the service provider will be sent by the higher capacity (preferre3d) WAN once it is retstored to service, or will the message be sent via the one to which fail over occurred (or the only one remaining in service)?
Thanks for the replies. I’m including a portion of my logs below. (I had to remove the full dyndns host name to post because the forum software considers it a link.)
I think it does update properly on failover and recovery at least some of the time. Based on the log, it updated correctly on Aug. 3. But, on more than one occasion DDNS has been left on the mobile internet address.
This is particularly problematic because it isn’t just a slow link – it becomes a dead link. Since I don’t know the new primary WAN 1 IP after recovery, there’s no way to reach the router or my network remotely to correct the situation.
On Aug 6 after a power cycle, the log suggests that DDNS was updated for Mobile Internet even though WAN 1 was up and functional and Mobile was disconnected. That may have led to my most recent incident.
Aug 08 10:55:02 Admin: msdowdie (192.168.0.42) login successful
Aug 08 10:54:57 Admin: admin (192.168.0.42) login failed
Aug 07 14:25:58 System: Changes applied
Aug 07 14:22:42 Admin: msdowdie (192.168.0.99) login successful
Aug 07 14:16:29 Admin: msdowdie (192.168.0.99) login successful
Aug 06 17:35:59 System: Time synchronization successful
Aug 06 17:35:31 WAN: Mobile Internet disconnected (Cold standby)
Aug 06 17:35:25 DDNS: Domain dyndns updated successfully for Mobile Internet
Aug 06 17:35:24 DDNS: Domain dyndns updated successfully for Mobile Internet
Aug 06 17:35:24 WAN: Mobile Internet disconnected (Cold standby)
Aug 06 17:35:05 DDNS: Domain dyndns updated successfully for WAN 1
Aug 06 17:35:02 WAN: WAN 1 connected (73.2.195.8)
Aug 06 17:34:47 System: Started up (7.0.1 build 2988)
Aug 06 17:33:03 System: Started up (7.0.1 build 2988)
Aug 05 06:03:56 WAN: Mobile Internet disconnected (Cold standby)
Aug 05 06:03:50 DDNS: Domain dyndns updated successfully for WAN 1
Aug 05 06:03:49 WAN: WAN 1 connected (73.2.195.8)
Aug 05 06:00:32 DDNS: Domain dyndns updated successfully for Mobile Internet
Aug 05 06:00:31 WAN: Mobile Internet connected (10.21.140.121)
Aug 05 05:59:48 WAN: WAN 1 disconnected (No cable detected)
Aug 04 01:39:26 WAN: Mobile Internet disconnected (Cold standby)
Aug 04 01:39:16 DDNS: Domain dyndns updated successfully for WAN 1
Aug 04 01:39:15 WAN: WAN 1 connected (73.2.195.8)
Aug 04 01:22:12 DDNS: Domain dyndns updated successfully for Mobile Internet
Aug 04 01:22:11 WAN: Mobile Internet connected (10.89.192.158)
Aug 04 01:22:00 WAN: WAN 1 disconnected (WAN failed DNS test)
Aug 03 19:10:07 Admin: msdowdie (192.168.0.57) login successful
Aug 03 02:06:25 WAN: Mobile Internet disconnected (Cold standby)
Aug 03 02:06:16 DDNS: Domain dyndns updated successfully for WAN 1
Aug 03 02:06:15 WAN: WAN 1 connected (73.2.195.8)
Aug 03 00:15:30 DDNS: Domain dyndns updated successfully for Mobile Internet
Aug 03 00:15:29 WAN: Mobile Internet connected (10.15.217.57)
Aug 03 00:15:19 WAN: WAN 1 disconnected (WAN failed DNS test)
Jul 31 07:10:42 System: Changes applied
Jul 31 07:05:51 Admin: msdowdie (192.168.0.142) login successful
Jul 26 04:45:51 WAN: Mobile Internet disconnected (Cold standby)
Jul 26 04:45:42 DDNS: Domain dyndns updated successfully for WAN 1
Jul 26 04:45:41 WAN: WAN 1 connected (73.2.195.8)
Jul 26 04:41:36 DDNS: Domain dyndns updated successfully for Mobile Internet
Jul 26 04:41:35 WAN: Mobile Internet connected (10.168.29.83)
Jul 26 04:41:24 WAN: WAN 1 disconnected (WAN failed DNS test)
Jul 21 18:41:12 Admin: msdowdie (107.77.234.135) login successful
Jul 18 16:42:44 System: Changes applied
Jul 18 16:40:44 Admin: msdowdie (192.168.0.42) login successful
Jul 18 14:23:07 Admin: msdowdie (192.168.0.142) login successful
Jul 18 14:23:07 Admin: msdowdie (192.168.0.142) login successful
Jul 18 03:45:57 System: Time synchronization successful
Jul 18 03:45:30 WAN: Mobile Internet disconnected (Cold standby)
Jul 18 03:45:22 DDNS: Domain dyndns updated successfully for Mobile Internet
Jul 18 03:45:21 WAN: Mobile Internet disconnected (Cold standby)
I power cycled the Balance again as a test. It appears that after a power cycle, DDNS is initially updated to WAN 1 but is then updated for WAN 2 Mobile. WAN 2 Mobile is correctly disconnected in favor of WAN 1, but DDNS is not updated. So DDNS remains set to an invalid WAN 2 Mobile IP address. I confirmed this with lookups on a PC. The log and my tests on the PC are in agreement that the last DDNS update is for a Mobile address which then goes away.
Aug 08 11:29:17 System: Time synchronization successful
Aug 08 11:28:48 WAN: Mobile Internet disconnected (Cold standby)
Aug 08 11:28:41 DDNS: Domain msdowdie.dyndns.org updated successfully for Mobile Internet
Aug 08 11:28:40 WAN: Mobile Internet disconnected (Cold standby)
Aug 08 11:28:21 DDNS: Domain msdowdie.dyndns.org updated successfully for WAN 1
Aug 08 11:28:20 WAN: WAN 1 connected (73.2.195.8)
Aug 08 11:28:19 Admin: msdowdie (192.168.0.42) login successful
Aug 08 11:28:06 System: Started up (7.0.1 build 2988)
Good catch @cover. Base on the event logs, there may be a glitch for the DDNS update when the device startup. Let’s me further check on this and update the post shortly. If confirm the issue we sure can raise this for the fixes.
Suspected logs:
Occurrence 1:
Aug 06 17:35:31 WAN: Mobile Internet disconnected (Cold standby)
Aug 06 17:35:25 DDNS: Domain dyndns updated successfully for Mobile Internet
Aug 06 17:35:24 DDNS: Domain dyndns updated successfully for Mobile Internet
Aug 06 17:35:24 WAN: Mobile Internet disconnected (Cold standby)
Aug 06 17:35:05 DDNS: Domain dyndns updated successfully for WAN 1
Aug 06 17:35:02 WAN: WAN 1 connected (73.2.195.8)
Aug 06 17:34:47 System: Started up (7.0.1 build 2988)
Occurrence 2:
Aug 08 11:29:17 System: Time synchronization successful
Aug 08 11:28:48 WAN: Mobile Internet disconnected (Cold standby)
Aug 08 11:28:41 DDNS: Domain msdowdie.dyndns.org updated successfully for Mobile Internet
Aug 08 11:28:40 WAN: Mobile Internet disconnected (Cold standby)
Aug 08 11:28:21 DDNS: Domain msdowdie.dyndns.org updated successfully for WAN 1
Aug 08 11:28:20 WAN: WAN 1 connected (73.2.195.8)
Aug 08 11:28:19 Admin: msdowdie (192.168.0.42) login successful
Aug 08 11:28:06 System: Started up (7.0.1 build 2988)
@Rick-DC
DYNDNS update using the same hostname/domain for the WANs as for now only suggested for Active Standby WAN deployment. DYNDNS update will send when WAN Status changed.
Tried to simulated this in my device but i failed to reproduce the isssue. Please check the logs below:
Aug 09 02:24:54 DDNS: Domain mypeplink.myftp.info updated successfully for WAN 1
Aug 09 02:24:52 WAN: WAN 1 connected (192.168.52.27)
Aug 09 02:24:23 WAN: Mobile Internet disconnected (No device detected)
Aug 09 02:24:08 DDNS: Domain mypeplink.myftp.info updated successfully for Mobile Internet
Aug 09 02:24:07 WAN: Mobile Internet connected to Celcom (10.120.149.1)
Aug 09 02:23:53 WAN: WAN 1 disconnected (No cable detected)
Aug 09 02:17:04 DDNS: Domain mypeplink.myftp.info updated successfully for WAN 1
Aug 09 02:17:02 WAN: WAN 1 connected (192.168.52.27)
Aug 09 02:16:51 WAN: Mobile Internet disconnected (No device detected)
Aug 09 02:12:26 DDNS: Domain mypeplink.myftp.info updated successfully for Mobile Internet
Aug 09 02:12:25 WAN: Mobile Internet connected to Celcom (10.147.99.247)
Aug 09 02:12:07 WAN: WAN 1 disconnected (No cable detected)
Aug 09 02:07:54 Admin: admin (192.168.2.10) login successful
Aug 09 02:07:50 System: Time synchronization successful
Aug 09 02:07:03 DDNS: Domain mypeplink.myftp.info updated successfully for WAN 1
Aug 09 02:07:00 WAN: WAN 1 connected (192.168.52.27)
Aug 09 02:06:37 System: Started up (7.0.1 build 2988)
May i know any specific steps to reproduce the issue ? Just reboot the device ?
From the logs below:
Occurrence 1:
Aug 06 17:35:24 WAN: Mobile Internet disconnected (Cold standby)
Aug 06 17:35:05 DDNS: Domain dyndns updated successfully for WAN 1
Occurrence 2:
Aug 08 11:28:40 WAN: Mobile Internet disconnected (Cold standby)
Aug 08 11:28:21 DDNS: Domain msdowdie.dyndns.org updated successfully for WAN 1
I see that around 20 seconds gap when the Mobile Internet disconnected. Anything to do to triggered the disconnection ?
I did nothing but simply pull the power cord on the Balance One, then power it back up. WAN 1 link remained up and available while the Balance rebooted. WAN 2 USB cellular modem remained attached.
I don’t see why it would ever update DDNS with the WAN 2 cellular ip during the boot process. It should just use WAN 1.
It appeared to connect to WAN 1 quickly after booting and did not appear to disconnect from WAN 1 or connect to WAN 2.
If I recall correctly, each WAN connection handles its dynamic DNS separately. I had hoped that there would be one master dynamic DNS that is updated whenever the WAN connection changes, but that is not the case. In the end, I set up a different ddns host names for each WAN connection and they update independently. This severely limits the usefulness of the router’s ddns for me, so I run a separate ddns update client on a PC with a third host name to act as the master/current ddns address.
Thanks. That seems pretty absurd given the intended use of the Peplink routers. I need to be able to point to 1 location. My primary is Comcast and backup is Verizon AC791L here and after this Comcast outage it ended up hanging with Verizon DDNS as the last update despite Comcast coming back online.
Having something that pushes a DDNS update after WAN cycling seems pretty basic. I didn’t have an issue in my much older & cheaper Cradlepoint MBR1400 before this Peplink Balance 305 or a Netgear FVX before that.
I’m aware of the mypeplink service but strongly prefer to use dyndns because of it’s integration with other systems.
My situation is similar. Comcast with backup failover to AT&T cellular. It would be helpful for the that the router to update a DDNS host to the current active WAN IP.
However, I also found recently that the AT&T cellular WAN IP address is next to useless because it is behind carrier level NAT. Nothing can initiate a connection from the internet back to the NATed IP address.
To solve this, I’d need either a VPN connection or maybe SpeedFusion so that the router is actually reachable when using the AT&T cellular WAN. Comcast isn’t currently unreliable enough to justify the time and trouble.
We paid for a dedicated IP with Verizon and had an LG-VL600 with our Cradlepoint which worked well until they deprecated the 4G bands it uses. I think we’ll end up on SpeedFusion using a Vultr instance but want the failover to work before we get to that thus needing DDNS to work correctly in the Peplink Balance 305. It looks like the Verizon USB730L might work instead of our AC791L and maybe a direct USB modem on AT&T would work for you if they offer a business IP service like Verizon does (for a fee).
The dedicated IP is a good suggestion. Right now, my backup AT&T connection is $10/month using a family shared data plan. It keeps us going inside the LAN if Comcast when Comcast is down. It would be good to have a solution that allows incoming connections over AT&T. It would take a lot more downtime on Comcast to justify the money and effort to pay for a dedicated IP.
First of all, you need a routable IP address - one reachable from the outside. If your connections are behind a (carrier) NAT then you need to set up a connection to (and by way of) some outside router, e.g., a fusionhub.
Secondly, assume that you have routable IP address(es) to the WAN interface(s) of the device (be they dynamic or static) then Peplink is offering a DNS name for each interface of the device though its Incontrol2 registration. And in particular it defines a hostname for the IP address employed by the device to connect to IC2. That may vay over time (as connections are enabled or disabled).
E.g., assume your router is a Balance One, with two WAN interfaces. Assume further that you have named it “MyBalanceOne” in IC2, and have activated the “Find My Peplink Address” feature.
Your internet hostname will then be “MyBalanceOne.mypep.link”
Your WAN-1 interface will be “wan-1.MyBalanceOne.mypep.link” and whatever IP address the device connects to IC2 will be “ic2-detected.MyBalanceOne.mypep.link”. As the WANs go up or down, the “ic2-detected.MyBalanceOne.mypep.link” will change (though I don’t know how frequently that is being updated).
That might do the trick for you.
A couple of things to keep in mind:
The IP address of ic2-detected.MyBalanceOne.mypep.link will be wherever the breakout is for communications to IC2 from the device. If the device is behind a carrier NAT then the IP address will be that of the gateway to the internet, and not (by itself) usable. But
If the device is connected to a fusionhub (or other gateway device) and traffic is routed through that gateway then the IP address of ic2-detected.MyBalanceOne.mypep.link will be one that you control, and would allow you to set up the proper port or address forwarding from the gateway to the device.
