# After upgrade, docker cannot communicate with the outside world

**URL:** https://meta.discourse.org/t/after-upgrade-docker-cannot-communicate-with-the-outside-world/171902
**Category:** Self-hosting
**Created:** [December 1, 2020, 5:43pm UTC](https://meta.discourse.org/t/after-upgrade-docker-cannot-communicate-with-the-outside-world/171902 "2020-12-01T17:43:28Z")
**Posts on this page:** 1
**Showing post:** 25

<div class="post-metadata">

### Author: ![yanokwa](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/yanokwa/32/105083_2.png) [@yanokwa](https://meta.discourse.org/u/yanokwa)
#### Post date: [January 3, 2021, 11:06pm UTC](https://meta.discourse.org/t/after-upgrade-docker-cannot-communicate-with-the-outside-world/171902/25 "2021-01-03T23:06:57Z")

</div>

One thing that I’ve noticed recently in Ubuntu 20 on DigitalOcean is that the host machine doesn’t make its domain name servers available to Docker. This is not an issue with the firewall because Ubuntu 20 doesn’t come with the firewall enabled.

To fix, first find the DO name servers with `cat /run/systemd/resolve/resolv.conf`. You’ll see something like this…

```plaintext
nameserver 1.2.3.4
nameserver 9.8.7.6

```

Next, edit the daemon.json file with `nano /etc/docker/daemon.json` to make those nameservers, and optionally, the Google DNS (8.8.8.8) are available to Docker.

```json
{
    "dns": ["<ip1 from above>", "<ip2 from above>", "8.8.8.8"]
}

```

Then restart Docker and rebuild.

```plaintext
systemctl restart docker
/var/discourse/launcher rebuild app

```

---

_[View the full topic](https://meta.discourse.org/t/after-upgrade-docker-cannot-communicate-with-the-outside-world/171902)._