I am trying to get to the bottom of the issue. Likely it was AWS’s own custom DNS resolver that uses DynamoDB.

Reply to this note

Please Login to reply.

Discussion

No replies yet.