# Unable to resolve any domains

**URL:** https://discourse.pi-hole.net/t/unable-to-resolve-any-domains/39054
**Category:** docker
**Created:** [October 5, 2020, 4:36am UTC](https://discourse.pi-hole.net/t/unable-to-resolve-any-domains/39054 "2020-10-05T04:36:34Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![plc0](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/plc0/32/18954_2.png) [@plc0](https://discourse.pi-hole.net/u/plc0)
#### Post date: [October 5, 2020, 4:36am UTC](https://discourse.pi-hole.net/t/unable-to-resolve-any-domains/39054/1 "2020-10-05T04:36:35Z")

</div>

my pihole is running via portainer on a raspberry pi 4. even when I ssh into the container, I get a resolution error:

```auto
sudo docker exec -it pihole /bin/bash
sudo: unable to resolve host pitron: Name or service not known
root@pihole:/#

```

but I can then attach successfully to the container.

this is the output of pihole -debug: [gist:91e673652558ba0fef198a9f9f9b029a · GitHub](https://gist.github.com/plc/91e673652558ba0fef198a9f9f9b029a)

it says:

`172.17.0.3/16 does not match the IP found in /etc/pihole/setupVars.conf`

in that file it says:

`IPV4_ADDRESS=0.0.0.0`

and whenever I update it with 172.17.0.3 it gets overwritten back to 0.0.0.0?

if I run dig ns1.pi-hole.net:

```auto
root@pihole:/# dig ns1.pi-hole.net

;; reply from unexpected source: 172.17.0.1#53, expected 192.168.7.8#53

```

and yet using @8.8.8.8 works fine:

```auto
root@pihole:/# dig ns1.pi-hole.net @8.8.8.8

; <<>> DiG 9.10.3-P4-Debian <<>> ns1.pi-hole.net @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30871
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512

;; QUESTION SECTION:
;ns1.pi-hole.net. IN A

;; ANSWER SECTION:
ns1.pi-hole.net. 3599 IN A 185.136.96.96

;; Query time: 147 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Oct 05 04:04:06 UTC 2020
;; MSG SIZE rcvd: 60

```

any help would be much appreciated!!! 😭

---

<div class="post-metadata">

### Author: ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)
#### Post date: [October 5, 2020, 9:27pm UTC](https://discourse.pi-hole.net/t/unable-to-resolve-any-domains/39054/2 "2020-10-05T21:27:28Z")

</div>

(_For your own privacy and security, please do not post your full, unsanitised debug log output. When providing a debug token, please post **just the token** that is shown once the debug finishes, preferably by copy and paste._)

Your issues are likely related to correctly configuring [Docker's network driver](https://docs.docker.com/network/).

Also, you are trying to tamper with the Docker image in ways not advisable, e.g. by running updates on your Pi-hole or its OS from within the container:

```auto
E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists/
root@pihole:/# sudo !!
sudo apt-get update

```

Note that any such changes you apply to a container would not survive a container restart.

In addition, you seem to have altered some of Pi-hole's default web server's configurations:

```auto
*** [DIAGNOSING]: contents of /etc/lighttpd
-rw-r--r-- 1 root root 4066 Oct 5 03:57 /etc/lighttpd/lighttpd.conf
   include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
   include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\"' 2>/dev/null"

```

I doesn't seem you are using Pi-hole's [official Docker](https://github.com/pi-hole/docker-pi-hole#docker-pi-hole) image at all?

---

<div class="post-metadata">

### Author: ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)
#### Post date: [October 6, 2020, 12:33am UTC](https://discourse.pi-hole.net/t/unable-to-resolve-any-domains/39054/3 "2020-10-06T00:33:14Z")

</div>

> [@plc0](#):
>
> `sudo: unable to resolve host pitron: Name or service not known`

That's a warning from `sudo`, it doesn't actually stop or break anything. `sudo` tries to look up the host name since you can have per host `sudo` rules. Easy solution to that is to put `pitron` in your `/etc/hosts` file with localhost as the address.

---

<div class="post-metadata">

### Author: ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)
#### Post date: [October 27, 2020, 12:33am UTC](https://discourse.pi-hole.net/t/unable-to-resolve-any-domains/39054/4 "2020-10-27T00:33:18Z")

</div>

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
