# Any other locations where database connection IP / hostname set other than DISCOURSE\_DB\_HOST in app.yml? **URL:** \ **Category:** Product Support\ **Created:** [May 23, 2021, 2:12am UTC](https://meta.discourse.org/t/any-other-locations-where-database-connection-ip-hostname-set-other-than-discourse-db-host-in-app-yml/191336 "2021-05-23T02:12:38Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![mreach](https://avatars.discourse-cdn.com/v4/letter/m/9d8465/32.png) [@mreach](https://meta.discourse.org/u/mreach)\ **Post date:** [May 23, 2021, 2:12am UTC](https://meta.discourse.org/t/any-other-locations-where-database-connection-ip-hostname-set-other-than-discourse-db-host-in-app-yml/191336/1 "2021-05-23T02:12:38Z")
Are there any other database connection definition locations other than the `DISCOURSE_DB_HOST` in `/var/discourse/containers/app.yml`? I have my PostgreSQL server running separately from my Discourse docker server and recently I changed the database connection hostname from the database server’s public hostname/IP to a private LAN IP. I’m seeing some connections on this private LAN IP now, but I’m still seeing most of the traffic go through the public IP / interface instead. I’ve tried to check the filesystem across the server and within the Docker Discourse image, but I’m not finding the old hostname or the old IP in any of these locations, but something is still accessing the public network interface from this Discourse installation. Any thoughts on how to isolate why Discourse would still be trying to talk to the wrong IP now? --- _[View the full topic](https://meta.discourse.org/t/any-other-locations-where-database-connection-ip-hostname-set-other-than-discourse-db-host-in-app-yml/191336)._