We’re hosting a dedicated Postgres 14 instance (fra1) and around a week ago, we started seeing errors of this sort:
Could not translate host name "db_name.b.db.ondigitalocean.com" to address: Temporary failure in name resolution.
The errors happen quite randomly and we can’t figure out the cause. We checked for traffic spikes and bot activity but none were present. As far as we know, we didn’t make any changes that could cause this issue.
We checked the DB load graphs and everything seems normal. CPU usage is the same as before (around 20%), RAM usage is around 75%, and disk space is at 40%. The load is also normal on the droplet connecting to the DB.
We also tried changing the systemd-resolved
DNS config to 8.8.8.8 and 1.1.1.1
servers but it didn’t help.
If we try to ping the DB hostname from the droplet connecting to the DB instance, the pings work normally.
Can somebody from the DO team check if there are some issues on the DO side?
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.
Hey @bartolfreskura,
As far as I can see there was an incident affecting Managed Databases Control Plane:
This could explain the intermittent issue that you were seeing but should be all resolved now.
If you are still seeing that issue, please reach out to the DigitalOcean support team who will be able to further investigate this for you:
Hope that helps!
- Bobby.