# Custom nameserver in Docker container

**URL:** <https://meta.discourse.org/t/custom-nameserver-in-docker-container/39716>\
**Category:** Product Support\
**Created:** [17.Февраль.2016 04:17:15 UTC](https://meta.discourse.org/t/custom-nameserver-in-docker-container/39716 "2016-02-17T04:17:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![andybalholm](https://avatars.discourse-cdn.com/v4/letter/a/b487fb/32.png) [@andybalholm](https://meta.discourse.org/u/andybalholm)\
**Post date:** [26.Февраль.2016 19:59:24 UTC](https://meta.discourse.org/t/custom-nameserver-in-docker-container/39716/4 "2016-02-26T19:59:24Z")

</div>

More strangeness:

I rebuilt the Discourse container, and edited `resolv.conf` to be just `nameserver 10.33.55.1`, and I could immediately resolve hostnames correctly. But whenever I restart the container, the contents of `resolv.conf` changes to:

```
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 10.33.55.1

```

So something is running when the container starts, and adding the Google nameservers to `resolv.conf`. Or does the container filesystem revert to its previous state whenever it is restarted?

---

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