DNS error when running cmdlets

[tfbryan]

Last Tuesday, June 13th, all cmdlets started returning DNS related errors. I can resolve the base domain name of amazonaws.com but not any of the subdomains such as ec2.d.amazonaws.com, acm.d.amazonaws.com, elasticloadbalancing.d.amazonaws.com, etc.

I upgraded all tools to the latest version (4.1.355) just in case there was a major change but the errors persist.

I know that I'm authenticated ok because I can run aws cli cmds just fine. I have to assume this is happening for others too?

[ashishdhingra]

@tfbryan Good morning. Thanks for starting the discussion. Unfortunately, I'm unable to reproduce the issue.

• Installed the latest AWS PowerShell modules using command Install-AWSToolsModule AWS.Tools.ElasticLoadBalancingV2 -CleanUp (used -Cleanup parameter to uninstall old versions of this module, if already installed). This installed version 4.1.356.0 of this module.
• Followed blog post Response Logging in AWS Tools for Windows PowerShell to enable verbose logs.

Add-AWSLoggingListener MyAWSLogs /tmp/logsaws.txt
Set-AWSResponseLogging Always
Enable-AWSMetricsLogging

• Executed the CmdLet Get-ELB2LoadBalancer.
• Examined the verbose logs written in /tmp/logsaws.txt

Amazon Information: 0 : Resolved DefaultConfigurationMode for RegionEndpoint [us-east-2] to [Legacy].
Amazon Information: 0 : Starting a process with the following ProcessInfo: UseShellExecute - False RedirectStandardError - True, RedirectStandardOutput - True, CreateNoWindow - True
Amazon Information: 1 : Process started
Amazon Information: 0 : Process ends with exitcode - 0
Amazon Verbose: 0 : Received response (truncated to 1024 bytes): [<DescribeLoadBalancersResponse xmlns="http://elasticloadbalancing.amazonaws.com/doc/2015-12-01/">
  <DescribeLoadBalancersResult>
    <LoadBalancers/>
  </DescribeLoadBalancersResult>
  <ResponseMetadata>
    <RequestId>52e66087-abe4-4048-8b77-bddd50d1959e</RequestId>
  </ResponseMetadata>
</DescribeLoadBalancersResponse>
]
Amazon Information: 1 : Request metrics: AsyncCall = True; CanonicalRequest = POST\n/\n\ncontent-type:application/x-www-form-urlencoded; charset=utf-8\nhost:elasticloadbalancing.us-east-2.amazonaws.com\nuser-agent:AWSPowerShell.Common/4.1.356.0 .NET_Core/7.0.5 OS/Darwin_22.5.0_Darwin_Kernel_Version_22.5.0:_Mon_Apr_24_20:53:44_PDT_2023;_root:xnu-8796.121.2~5/RELEASE_ARM64_T8103 PowerShellCore/7.-1 ClientAsync\nx-amz-content-sha256:291737628a8822c591d69bcc8ab0023e2d91be3e5358172d89f534bec412a356\nx-amz-date:20230621T181618Z\nx-amz-security-token:IQoJb3JpZ2luX2VjEGsaCXVzLWVhc3QtMSJGMEQCIHclktvCowXrVoS4kUdJcfhIeWwHm7j5Cwjb281lUPnJAiABwRbjPOq47xkybKDXfIznZfq1X+qDswROKxSRUHvw9iqmAgjD//////////8BEAEaDDEzOTQ4MDYwMjk4MyIMufr350P8TDZxm7QUKvoBDJI1P17TnteRRbI85GbLiu5y8Pn3BFeKTgKjaCo14RnCQBbVeMw6qlc8kyuEYdOGXmZCNmm/uUwY2TEgnOM5+NDCBuFIQTNvF47vaef7XOoc4NlGBJNhSDoOOrQ8tMUEKWZDB3Gxsip8C0iuUX6FJcp2iFwUfa6ycH4B2Jv/87/hnNtmTt9zcs4Z7L0WBUOjO6Yt9ip56y21yola0yyU3xIWfgi//63NYrJjJ22zZCdtH2C/l8q4vkYXPT2GraXyCDf3qdZVMjJdBlccbI5u74sHwRhloVXT6GxeR8Ja9ss68NTADZf/Sxrs+WV4pLrepVF60G7551G5vzDy/MykBjqeAcqg/pB/Nb1dITIToL+SwBlLh3QNsmZriymlN0xoIlLnnopN2fbjxlf8WhYSeDET0/dMMhypZqZ5eWqALYhzeA8+l9AE5WriX1tWSJkebB5JtRLJ3RUL/lC+LJHUeV93mGW4S2aby7+2HVMrWXKMUFbaoBXvqK/LLdzBZg2AAKykSgU7e4x13vsuii5gOj6z0WIjTKbWJqo21tJzCvht\n\ncontent-type;host;user-agent;x-amz-content-sha256;x-amz-date;x-amz-security-token\n291737628a8822c591d69bcc8ab0023e2d91be3e5358172d89f534bec412a356; StringToSign = AWS4-HMAC-SHA256\n20230621T181618Z\n20230621/us-east-2/elasticloadbalancing/aws4_request\n4c971bb5aa5c3a43033c7e2897a2ff46f0f86440a4c15a4520dbeade742b0b67; ServiceName = Amazon.ElasticLoadBalancingV2; ServiceEndpoint = https://elasticloadbalancing.us-east-2.amazonaws.com/; MethodName = DescribeLoadBalancersRequest; RequestSize = 47; StatusCode = OK; BytesProcessed = 324; AWSRequestID = 52e66087-abe4-4048-8b77-bddd50d1959e; CredentialsRequestTime = 00:00:01.9713513; RequestSigningTime = 00:00:00.0007253; HttpRequestTime = 00:00:00.4038989; ResponseUnmarshallTime = 00:00:00.0007513; ResponseProcessingTime = 00:00:00.0034622; ClientExecuteTime = 00:00:02.3809458;

Service endpoint elasticloadbalancing.us-east-2.amazonaws.com is being hit.

I'm unsure why in your case, it's hitting the endpoint elasticloadbalancing.d.amazonaws.com:443. Could you check the region set in your dev profile, looks like it is erroneously set to value d?

Thanks,
Ashish

[tfbryan]

Thanks so much for the reply and the suggestion. I did check my profile just now and in fact the default profile is set to "d" which I'm sure I did while testing something. The interesting thing is that when using the modules, I am using named profiles which do have proper values. Does the endpoint get created based off default profile values?

[ashishdhingra]

@tfbryan The region resolution happens here with all the generators. It should have picked the region from the named profile.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.