SmartServer IoT Signed Certificates and DDNS Issues with 2.80 (KB1406)

The following Signed Certificates and DDNS issues only apply to SmartServer IoT 2.80

DDNS Not Updating Correctly AP-7544

Turning on signed certificates may update the DDNS entry for the external address of the SmartServer incorrectly. This is due to an error in /sbin/aws-update

This is the incorrect line in aws-update:

# Get the external IP address from OpenDNS (more reliable than other providers)
IP=`dig +short myip.opendns.com`

This is the how it should be changed:

# Get the external IP address from OpenDNS (more reliable than other providers)
IP=`dig +short myip.opendns.com @resolver1.opendns.com`

DDNS may not be updated correctly every 30 minutes AP-7625

After the above fix, DDNS will may not update every 30 minutes, the work around is to manually call the following command if needed from a console connection logged in as root (not sudo) 

/sbin/aws-update

 Signed Certificates Not Working After a Re-Image AP-7611

Enabling signed certificates may not work correctly after a re-image and DDNS may not update the external address of the SmartServer.

 The work around is to use the following three lines from the console when logged in as root (not sudo). 

1. rm /sbin/update-route53.*
2. /sbin/get-cert
3. /sbin/use-cert secure