Every so often a droplet will start throwing this error out of the blue:
“Temporary failure in name resolution”
PHP error (redacted):
{"error":{"msg":"php_network_getaddresses: getaddrinfo for xxx-000000-do-user-000000-0.b.db.ondigitalocean.com failed: Temporary failure in name resolution","code":2002}}
It’s occurring because it’s trying to make a SQL connection to a DO managed DB.
The issue only occurs from THAT droplet, no other. Other droplets can communicate with the managed DB without issue. I can even remotely connect to the Managed DB and can see that it’s running fine. The issue is purely isolated to the one droplet at that moment.
Then, after about 10-15 minutes, the issue resolves and the said droplet starts talking to the managed DB again.
What causes this? The instances of it occurring a very random, from different droplets, usually without any significant or unusual activity or process. The fact that we can connect into the managed DB remotely suggests that it’s an internal issue within DO.
A few articles here suggest that it’s a DNS issue
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Sign up for Infrastructure as a Newsletter.
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Same thing here, it happens often, but the database remains online. It seems to happen during high traffic, or when bots/crawlers are on the website.
This comment has been deleted
It’s still happening from time to time, this one was just a few minutes ago:
There are no noted networking issues by DO. It’s only affecting on Droplet in system, others within the same VPC are functioning fine and I can otherwise query the database remotely.
Very strange and annoying