Project

General

Profile

Actions
Copy link

Bug #7900

closed

DynamicDNS Amazon Route53 Not Working

Added by George 77 over 6 years ago. Updated over 6 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
Dynamic DNS
Target version:
-
Start date:
09/29/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.x
Affected Architecture:
All

Description

DynamicDNS Provider Route53 is not updating. Despite the failure, the error detection code doesn't catch that a failure response (403) is received from Amazon, and reports to the user that the DNS update was successful. It seems to me the actual bug needs to be fixed, the error detection code needs to be improved (currently only looks for one specific error), and an extra check needs to occur to verify the change did actually get committed at Route53. Here is the specific error in my situation. I'm still trying to figure out what is wrong/changed because the request looks correct.

AmHTTP/1.1 403 Forbidden
x-amzn-RequestId: 7-----------------------
Content-Length: 152
Date: Thu, 28 Sep 2017 12:42:19 GMT


<AccessDeniedException>
<Message>Unable to determine service/operation name to be authorized</Message>
</AccessDeniedException>

Actions
Copy link
 #1

Updated by George 77 over 6 years ago

It looks like the settings for the HostZonedID input were changed (previously needed to specify a region and hosted zone ID), now the region is hard coded in to the dynamicdns.class. This could probably be changed to an enhancement for better error detection and also validation of a successful update, but at least it isn't broken.

Actions
Copy link
 #2

Updated by Jim Pingle over 6 years ago

  • Status changed from New to Not a Bug
  • Target version deleted (2.4.1)
Actions
Copy link

Also available in: Atom PDF