All updates are sent using a well-formed HTTP request.
Dyn will pass back a return code that the client needs to parse. If you have questions about the syntax, please contact Dyn support. It is not necessary to open any incoming ports (or allow incoming ICMP) for updating.
Configuration of dyndns seams to be working in the ERL but the IP address is not updated at the side.
When a change in IP address is found or a user alters any of their settings, the client should perform an update.
The update client periodically checks your network’s IP address; if it sees that your IP address has changed, it sends (updates) the new IP address to your hostname in your Dyn account.
If you’re like many Dyn DNS customers, you have a dynamic IP address which changes periodically (monthly, weekly or even daily).
So it seems that the only the Actiontec's are not communicating with DYNDNS.**EDIT - I deleted and recreated the DYNDNS host in both Actiontec devices - no luck.. Thanks I checked the Actontec logs and I see the following entries after I try to manually update within the device: Apr 23 2014 System Log Message No response from server Apr 23 2014 System Log Message Error connecting to host Apr 23 2014 System Log Message estream_connect_ssl_efd 39: failed ssl connetion The first thing that caught my eye was the mis-spelling of "Connection"My second thought was "SSL".though I have SSL set to NONE.
Rebooted both devices as well.**Edit 2 - I just checked a 2rd remote device.. Maybe this is heartbleed issues and Dyn DNS is preventing any connections from certain devices? I've been meaning to contact them asking if they have any idea why this is.Hi, I just bought and configured my first ERL but I can't seam to get dyndns to actually update my records.