There are quite a few older requests and bug reports about dynamic DNS. This needs to be addresses in a consolidated fashion.
FOr anyone not familiar with dynamic DNS, this is where you use a service such as dyndns.com to register host names like mypeplinkxx.dyndns-ip.org and this hostname always points to the current public IP of the pepwave, becasue every time the IP changes the pepwave updates the IP at dyndns.
The issue seems to be that engineering only considered dynamic dns for dynamic IPs on a WAN link. And of course it is used for that. But more frequently it is needed to update a dynamic host name when a pepwave switches to cellular and back.
It ALMOST works perfectly for this, and we have it set this way on about 40 pepwaves.
The only issue we have (and it is a real problem) is that sometimes the update seems to fail. the event log shows that it was updated, but dyndns still has the previous IP. I believe that this is a timing issue. One thing I have observed is that it ALWAYS seems to be when the unit switches from cellular back to WAN, but dyndns still shows the cellular IP.
This means that applications using that dynamic host name now fail until we notice that failure and manually correct the IP.
This happens perhaps once every few days to one unit or another.
Suggestion: The pepwave can test the hostname a minute after making the change. If it has not updated, send the update again. If it fails several times, perhaps that should be a notifiable event.