Dynamic DNS - Route53 errors should probably be more verbose
This is somewhat related to Bug #3973.
I have a system where the "password" for the Route53 DynamicDNS handler kept getting reset to something not-correct (I suspect LastPass was trying to be "helpful" and was changing it). There is no outwardly visible sign that this password wasn't working, until you click back to the dashboard and get the banner mentioning that there is a crash dump to view. I had to less /tmp/PHP_errors.log in order to figure out that not only was the IP not updating, there was a password problem. The GUI is displaying the IP in green as though everything is fine, when this isn't actually the case.
#4 Updated by Braden McGrath over 5 years ago
70.60.165.x, I just submitted again.
When the password is incorrect (presumably similar error with a bad username?):
[31-Aug-2015 21:12:50 America/New_York] PHP Warning: Route53::changeResourceRecordSets(): Sender - SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. Request Id: 907ef4a0-5046-11e5-bef7-670155c3dc0a in /etc/inc/r53.class on line 545
Alternatively, password is correct, but an error in the hostname, in this instance an extra period at the end: (making it a truly FQDN but apparently AWS doesn't like this)
[31-Aug-2015 21:17:22 America/New_York] PHP Warning: Route53::changeResourceRecordSets(): Sender - InvalidChangeBatch: FATAL problem: DomainLabelEmpty encountered at my-valid.fqdn.com. Request Id: 324c2883-5047-11e5-991a-a7c5d9388a4e in /etc/inc/r53.class on line 545