Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"no such host" / NXDOMAIN error. Terraform retries for more than an hour. #2427

Closed
joernheissler opened this issue Nov 25, 2017 · 6 comments
Closed
Labels
question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com.

Comments

@joernheissler
Copy link

Hello!

Terraform took more than an hour to notice that a resource cannot be created.
In my opinion, this should have been an immediate error.

* aws_ses_domain_identity.sub: Error requesting SES domain identity verification:
    RequestError: send request failed
caused by: Post https://email.eu-central-1.amazonaws.com/:
    dial tcp: lookup email.eu-central-1.amazonaws.com on 127.0.0.1:53:
    no such host

email.eu-central-1.amazonaws.com does not exist, my dns server on 127.0.0.1 responds with NXDOMAIN.

Terraform Version

Terraform v0.11.0
+ provider.aws v1.3.1

Affected Resource(s)

  • aws_ses_domain_identity

I assume that other resources are affected too.

Terraform Configuration Files

provider "aws" {
    region = "eu-central-1"
}

resource "aws_ses_domain_identityaws_ses_domain_identity" "sub" {
    domain = "test.example.net"
}

Debug Output

https://gist.github.com/joernheissler/e256c0c7704d300ba4c2674575796293

Expected Behavior

Immediate error.

Actual Behavior

aws_ses_domain_identity.sub: Still creating... (1h18m40s elapsed)

And only then it failed.

Steps to Reproduce

Try above configuration.

Important Factoids

There is no SES service in eu-central-1. I neglected to select the correct region.

@radeksimko radeksimko added the question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com. label Nov 26, 2017
@arnisoph
Copy link

arnisoph commented Dec 1, 2017

I was able to fix this by setting the correct region... (eu-west-1 instead of eu-central-1)

Thanks for the hint!

@arnisoph
Copy link

arnisoph commented Dec 1, 2017

this issue duplicates #732

@joernheissler
Copy link
Author

Thanks, I must have missed that one.

@elisiano
Copy link

@arnoldbechtoldt could you please provide more details of where you specified the region?

@arnisoph
Copy link

@elisiano either ~/.aws/credentials or in the provider definition

@ghost
Copy link

ghost commented Apr 2, 2020

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com.
Projects
None yet
Development

No branches or pull requests

4 participants