# Solve DNS Resolution in Other Containers when using Docker pihole

**URL:** <https://discourse.pi-hole.net/t/solve-dns-resolution-in-other-containers-when-using-docker-pihole/31413>\
**Category:** Community How-to's\
**Created:** [May 2, 2020, 12:56am UTC](https://discourse.pi-hole.net/t/solve-dns-resolution-in-other-containers-when-using-docker-pihole/31413 "2020-05-02T00:56:12Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![tackin](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/tackin/32/37940_2.png) [@tackin](https://discourse.pi-hole.net/u/tackin)\
**Post date:** [October 5, 2023, 8:59am UTC](https://discourse.pi-hole.net/t/solve-dns-resolution-in-other-containers-when-using-docker-pihole/31413/13 "2023-10-05T08:59:27Z")

</div>

The above solution for me is NOT the best.I would like to suggest a solution much easier and with absolutely no editing in any docker-compose.yml.  
In /etc/resolvconf.conf you just need to enable:  
nameserver 127.0.0.1  
... as written in this file itself:  
`# If you run a local name server, you should uncomment the below line and`  
`# configure your subscribers configuration files below.`

After this just do a  
sudo resolvconf -u  
to update the reslove-config. .. and of course redeploy your containers.

---

_[View the full topic](https://discourse.pi-hole.net/t/solve-dns-resolution-in-other-containers-when-using-docker-pihole/31413)._