Though the above changes did not help, I have moved all the resources into one v-net under one resource group, and that resolved it.
ENOTFOUND from one of my containerapp to ***.postgres.azure.com despite settingup peering, private dnszone and linking
ENOTFOUND from one of my containerapp to ***.postgres.azure.com despite settingup peering, private dnszone and linking
Azure Container Apps
2 answers
Sort by: Most helpful
-
-
Sai Prabhu Naveen Parimi 2,020 Reputation points Microsoft External Staff Moderator
2025-05-26T12:22:11.7+00:00 Thanks for the update and confirmation.
To summarize for anyone facing a similar issue:
You were encountering an
ENOTFOUND
error from the Azure Container App when trying to connect to***.postgres.azure.com
, even after setting up VNet peering, a private endpoint for PostgreSQL, and linking the appropriate private DNS zone.This issue was ultimately resolved by you moving all related resources (Container App, PostgreSQL server, DNS zone, etc.) into a single Virtual Network under one Resource Group.
Regarding your observation that the container image wasn’t updating:
This behavior is expected if the same tag (like
latest
) is reused. Azure Container Apps pulls images based on the image digest, not just the tag. If the digest doesn't change, the platform assumes it's the same image and doesn't redeploy. Using unique image tags or triggering a new revision helps Azure detect and apply changes as expected.Please do not forget to click "Accept the answer” and
Yes
wherever the information provided helps you, this can be beneficial to other community members.