dial tcp: lookup route53domains.us-west-2.amazonaws.com on 192.168.1.1:53: no such host

[scalp42]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform v1.1.7
on darwin_arm64
+ provider registry.terraform.io/hashicorp/aws v4.4.0

Affected Resource(s)

aws_route53domains_registered_domain

Terraform Configuration Files

resource "aws_route53domains_registered_domain" "domain" {
  domain_name = "example.org"

  # NOTE: these are the defaults
  registrant_privacy = true
  auto_renew = true
  transfer_lock = true

  registrant_contact {
    organization_name = "changeme"
    first_name = "changeme"
    last_name = "changeme"
    email = "changeme@example.org"
    phone_number = "000-000-0000"
    address_line_1 = "xxxx"
    zip_code = "xxxx"
    state = "California"
    city = "San Francisco"
    contact_type = "COMPANY"
  }
}

Debug Output

https://gist.github.com/scalp42/26d80ebc579502955c3b7ec1858ebfd3

Expected Behavior

Domain shoud have been created.

Actual Behavior

It times out with a DNS error:

2022-03-11T11:41:08.698-0800 [WARN]  provider.terraform-provider-aws_v4.4.0_x5: Disabling retries after next request due to networking issue: https response error StatusCode: 0, RequestID: , request send failed, Post "https://route53domains.us-west-2.amazonaws.com/": dial tcp: lookup route53domains.us-west-2.amazonaws.com on 192.168.1.1:53: no such host: timestamp=2022-03-11T11:41:08.697-0800
2022-03-11T11:41:08.698-0800 [TRACE] provider.terraform-provider-aws_v4.4.0_x5: Called downstream: @module=sdk.proto tf_proto_version=5 tf_provider_addr=provider @caller=/opt/teamcity-agent/work/5d79fe75d4460a2f/pkg/mod/github.com/hashicorp/terraform-plugin-go@v0.5.0/tfprotov5/tf5server/server.go:608 tf_req_id=7bbd75c7-8925-3ef0-ae8f-700aa9415a82 tf_resource_type=aws_route53domains_registered_domain tf_rpc=ApplyResourceChange timestamp=2022-03-11T11:41:08.698-0800
2022-03-11T11:41:08.699-0800 [TRACE] provider.terraform-provider-aws_v4.4.0_x5: Served request: tf_provider_addr=provider tf_resource_type=aws_route53domains_registered_domain tf_rpc=ApplyResourceChange @caller=/opt/teamcity-agent/work/5d79fe75d4460a2f/pkg/mod/github.com/hashicorp/terraform-plugin-go@v0.5.0/tfprotov5/tf5server/server.go:614 @module=sdk.proto tf_proto_version=5 tf_req_id=7bbd75c7-8925-3ef0-ae8f-700aa9415a82 timestamp=2022-03-11T11:41:08.698-0800

╷
│ Error: error reading Route 53 Domains Domain (example.org): operation error Route 53 Domains: GetDomainDetail, exceeded maximum number of attempts, 9, https response error StatusCode: 0, RequestID: , request send failed, Post "https://route53domains.us-west-2.amazonaws.com/": dial tcp: lookup route53domains.us-west-2.amazonaws.com on 192.168.1.1:53: no such host

2022-03-11T11:41:08.722-0800 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = transport is closing"
2022-03-11T11:41:08.728-0800 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/hashicorp/aws/4.4.0/darwin_arm64/terraform-provider-aws_v4.4.0_x5 pid=89333
2022-03-11T11:41:08.728-0800 [DEBUG] provider: plugin exited

$❯ dig route53domains.us-west-2.amazonaws.com

; <<>> DiG 9.10.6 <<>> route53domains.us-west-2.amazonaws.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20835
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;route53domains.us-west-2.amazonaws.com.  IN A

;; AUTHORITY SECTION:
us-west-2.amazonaws.com. 5  IN  SOA dns-external-master.amazon.com. hostmaster.amazon.com. 2012085210 180 60 2592000 5

;; Query time: 16 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Mar 11 11:44:58 PST 2022
;; MSG SIZE  rcvd: 141

[ewbankkit]

@scalp42 Thanks for raising this issue.
The Route 53 Domains service is only available in the us-east-1 Region.
For now you can pin the provider to that Region but we should do as we do for some other services and hard-code the us-east-1 Region:

terraform-provider-aws/internal/conns/conns.go

Lines 1619 to 1623 in 392d1c1

	// Force "global" services to correct regions
	switch Partition {
	case endpoints.AwsPartitionID:
	globalAcceleratorConfig.Region = aws.String(endpoints.UsWest2RegionID)
	route53Config.Region = aws.String(endpoints.UsEast1RegionID)

[ewbankkit]

Relates #12711.

[github-actions]

This functionality has been released in v4.6.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[scalp42]

@ewbankkit following up on this, I tried again with 4.12.1 and it's a new issue now:

 Error: error reading Route 53 Domains Domain (domain.example): couldn't find resource

I've tried using provider in us-east-1 as well.

[ewbankkit]

@scalp42 Can you try running aws --region us-east-1 route53domains get-domain-detail --domain-name domain.example?

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.