# Custom nameserver in Docker container

**URL:** <https://meta.discourse.org/t/custom-nameserver-in-docker-container/39716>\
**Category:** Product Support\
**Created:** [17 Febbraio 2016, 4:17am UTC](https://meta.discourse.org/t/custom-nameserver-in-docker-container/39716 "2016-02-17T04:17:15Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [17 Febbraio 2016, 8:42am UTC](https://meta.discourse.org/t/custom-nameserver-in-docker-container/39716/2 "2016-02-17T08:42:53Z")

</div>

As far as I’m aware, the container’s `resolv.conf` is copied from the host. So, if the container host has Google’s nameservers, then that’s what the container will get. AFAIK, there’s no way for a container image, nor the command line, to override that behaviour. Of course, you can edit the container’s `resolv.conf` after it is started, but there’s nothing in the Discourse images to do that that I can find. Certainly, the [discourse.org](http://discourse.org) hosting, which uses the same images as are publically available, don’t override `resolv.conf` (it definitely gets copied in from the host).

---

_[View the full topic](https://meta.discourse.org/t/custom-nameserver-in-docker-container/39716)._