Why are we getting a temporary failure in name resolution for one of our codedeploy jobs.

0

We've double checked our resolv.conf settings and confirmed DNS is working on the instance. Are we hitting some kind of DNS quota here? https://us-west-1.console.aws.amazon.com/codesuite/codedeploy/deployments/d-DK3X9YR2J?region=us-west-1

[stderr]error pulling image configuration: Get https://prod-us-west-1-starport-layer-bucket.s3.us-west-1.amazonaws.com/f3ebb4-118139069697-febca158-fcb4-8691-5416-12213ec5f233/09333ef6-c54b-402e-bdbe-a506aae50ad8?X-Amz-Security-Token=IQoJb3JpZ2luX2VjEJX%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLXdlc3QtMSJGMEQCIDvxxOc2QHUZICVPv8z4JcO9guj9TFhOHz%2BhFNFcJ3xnAiBIxXYH%2BfSfjKa5Qfy27sX3THps6binPSUWk0GDEsU%2FcSrAAwguEAMaDDY0MTkwMjM0NjY5NCIMMiTs4I8IsHhsS7kjKp0DekQoQzo9dMIxxuZwbRVYz2K7odpA0iNNaT2Wyz1gKWNGCHhL1ofyMrt0INEQ9VsPpQ0rV357OmZgR1h2WZDX7cpmbRDkY9vBafNwwhsVI3yACmvQI%2BnBbZPQn2cL2sbBUu1CYOegiFm0R4VgZKJ6ofx%2B3kfDTR5FO6rBouF0GXkc2MSbn%2BLnIYvfJSFMj7E19CmGZxDCOj2HnK3cEDba2pMNjSxAc9YQBgyVEtC%2Faz7rZ7FiFE2CgNQrxifxVUaIRdNDSzLtdkDPX3OQP85rQODTsFSz8lhQOKy8U7XqVbILRQKxzOnrKZiaChMhyO1m3rkUE9DuPO7t%2F473QQuPDB6o%2B2OavSdlylDvsA6aJdcy%2B6rAaylirvQ5734f2Qy81Ek7nbwPq2dw4%2BSx7Sw8XPzVADXWz%2Fv%2BAics2Wk0nX01rz3psYH4BbDGNMSLEWzORzdqiDq5O1vPHTtfHul%2FtyeeVRULtIb2XHc8ms2%2FWd88DBHonBAgnzjO0GVi9Jgldd5ff7jt6sfeVuA%2BwCZes%2BkqPVDr0JRcTiSvCkww%2B8jnmAY6ogECc3hG9IbK8NDsMSvjW5unt5iaJaqLH9NvAAS1DXKWhkz8DS36MW4rM65NMwD2Fn3NfyGaVRZIQ7iHKM%2F4ksUpQxi68ObptEQjbE4di%2FkMOyH%2BZxuFq%2BskEMNvwTKDYcBClpi8UphJdxLqqXVfAithlYGd7GL2row%2FIzom9xMO9tUY5paxq6Bm%2BnAim2KPtS%2FwSWqhg5R3dMSAB%2FGysZY6efU%3D&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20220908T135103Z&X-Amz-SignedHeaders=host&X-Amz-Expires=3600&X-Amz-Credential=ASIAZK5C4QHDIWPJ2TM5%2F20220908%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Signature=e66c322896f64ba188ce5bd2f171cfb1e7dc014f2be30ab93a6a600db7e28f7b: dial tcp: lookup prod-us-west-1-starport-layer-bucket.s3.us-west-1.amazonaws.com: Temporary failure in name resolution
epitone
asked 2 years ago1003 views
1 Answer
0

Hello,

Was this working previously ?

If you are trying to have DHCP generate the /etc/resolv.conf file when starting/stopping the server, make sure to check your network configuration scripts to ensure that PEERDNS=yes.

It's likely your default DNS server is pointing to an IP address that is not capable of resolving DNS queries. You should check the DNS settings in the file that /etc/resolv.conf is pointing to. When you go to that file (/var/run/systemd/resolve/resolve.conf), look at the IP that is right next to the keyword namespace. You should set it to your router's IP address (which can be found with the command route -n. Look for the gateway column and take the one that's not 0.0.0.0) or you can also set it to a public DNS server such as 1.1.1.1, 8.8.8.8 etc.

Hope this helps !!

profile pictureAWS
SUPPORT ENGINEER
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions