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