sedating decongestants - Wrt54g not updating dyndns

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.

wrt54g not updating dyndns-76wrt54g not updating dyndns-86wrt54g not updating dyndns-52

If these instructions do not help for your particular Link Sys router, please consult the routers manual or call Link Sys support to determine if your router has DDNS capabilities.

If your Internet connection has a static IP address, it is not necessary to configure dynamic DNS service.

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 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 and have found it to be nearly 100% reliable when properly updated.

I’ve looked at the firmware release notes and I don’t see where any changes to this behavior have been discussed. @cover 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) . But, on more than one occasion DDNS has been left on the mobile internet address.

Please check the simulation logs below: Aug 08 DDNS: Domain mypeplink.updated successfully for WAN 1 Aug 08 WAN: Mobile Internet standby (10.248.4.201) Aug 08 WAN: WAN 1 connected (192.1) Aug 08 DDNS: Domain mypeplink.updated successfully for Mobile Internet Aug 08 WAN: Mobile Internet connected to Celcom (10.248.4.201) Aug 08 WAN: WAN 1 disconnected (WAN failed PING test) Aug 08 DDNS: Domain mypeplink.updated successfully for WAN 1 Aug 08 System: Changes applied Aug 08 DDNS: Domain mypeplink.updated successfully for WAN 1 Aug 08 WAN: Mobile Internet standby (10.248.4.201) Aug 08 System: Changes applied Aug 08 DDNS: Domain mypeplink.updated successfully for WAN 1 Aug 08 System: Changes applied Aug 08 WAN: Mobile Internet disconnected (Cold standby) Aug 08 DDNS: Domain mypeplink.updated successfully for WAN 1 Aug 08 WAN: WAN 1 connected (192.1) Aug 08 DDNS: Domain mypeplink.updated successfully for Mobile Internet Aug 08 WAN: Mobile Internet connected to Celcom (10.247.166.177) Aug 08 WAN: WAN 1 disconnected (WAN failed PING test) Aug 08 DDNS: Domain mypeplink.updated successfully for WAN 1 Aug 08 System: Changes applied Aug 08 WAN: Mobile Internet disconnected (Cold standby) Aug 08 DDNS: Domain mypeplink.updated successfully for WAN 1 Aug 08 WAN: WAN 1 connected (192.1) Aug 08 DDNS: Domain mypeplink.updated successfully for Mobile Internet Aug 08 WAN: Mobile Internet connected to Celcom (10.247.110.58) Do you find any logs indicate that the update fail for your device ? (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. This is particularly problematic because it isn’t just a slow link – it becomes a dead link.

This is the only issue I’ve had with the Balance One. 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.

Tags: , ,