# Vanilla v6 install - no local name resolution in logs

**URL:** <https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838>\
**Category:** docker\
**Tags:** docker, synology\
**Created:** [March 10, 2025, 10:29pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838 "2025-03-10T22:29:43Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![bc3tech](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bc3tech/32/30431_2.png) [@bc3tech](https://discourse.pi-hole.net/u/bc3tech)\
**Post date:** [March 10, 2025, 10:29pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/1 "2025-03-10T22:29:43Z")

</div>

Just started getting v6 installed, got the dashboard working and serving requests.

However, all requests show as coming from localhost ( `pi.hole` ) instead of the client from where they originated. This doesn't help w/ logging, tracing, etc.

My compose file is barely different than the plain vanilla one from docs.

```yaml
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    ports:
      # DNS Ports
      - "53:53/tcp"
      - "53:53/udp"
      # Default HTTP Port
      - "8080:80/tcp"
      # Default HTTPs Port. FTL will generate a self-signed certificate
      - "8443:443/tcp"
      # Uncomment the below if using Pi-hole as your DHCP Server
      #- "67:67/udp"
      # Uncomment the line below if you are using Pi-hole as your NTP server
      #- "123:123/udp"
    environment:
      # Set the appropriate timezone for your location from
      # https://en.wikipedia.org/wiki/List_of_tz_database_time_zones, e.g:
      TZ: 'America/Los_Angeles'
      # Set a password to access the web interface. Not setting one will result in a random password being assigned
      FTLCONF_webserver_api_password: ""
      # If using Docker's default `bridge` network setting the dns listening mode should be set to 'all'
      FTLCONF_dns_listeningMode: 'all'

      DNSMASQ_USER: 'root'

      FTLCONF_dns_upstreams: '1.1.1.3;1.0.0.3'
      FTLCONF_dns_reply_host_IPv4: '192.168.1.250'
    # Volumes store your data between container upgrades
    volumes:
      # For persisting Pi-hole's databases and common configuration file
      - './etc-pihole:/etc/pihole'
      # Uncomment the below if you have custom dnsmasq config files that you want to persist. Not needed for most starting fresh with Pi-hole v6. If you're upgrading from v5 you and have used this directory before, you should keep it enabled for the first v6 container start to allow for a complete migration. It can be removed afterwards. Needs environment variable FTLCONF_misc_etc_dnsmasq_d: 'true'
      #- './etc-dnsmasq.d:/etc/dnsmasq.d'
    # cap_add:
      # See https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
      # Required if you are using Pi-hole as your DHCP server, else not needed
      # - NET_ADMIN
      # Required if you are using Pi-hole as your NTP client to be able to set the host's system time
      # - SYS_TIME
      # Optional, if Pi-hole should get some more processing time
      # - SYS_NICE
    restart: unless-stopped

```

Changes I made

1. Enable root user (per warning/error I got when this wasn't there)
2. Set upstreams to CloudFlare's family servers (this is serving all machines on my family's home network)
3. Set reply host to previous value of `ServerIP` from v5.

PiHole creates its default **bridge** network (this is where I believe the problem is) and everything works just fine.  
I've tried setting up `macvlan` and `host` and have yet to be successful or find a working **v6 config** anywhere.

What's a guy gotta do to host pihole in docker and get LAN name resolution to work in the logs & clients view of the dashboard?

---

<div class="post-metadata">

**Author:** ![Ladrien](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/ladrien/32/39018_2.png) [@Ladrien](https://discourse.pi-hole.net/u/Ladrien)\
**Post date:** [March 10, 2025, 10:43pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/2 "2025-03-10T22:43:19Z")

</div>

Can you send a picture of some sample queries? Specifically looking for the IP addresses of the clients.

---

<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:** [March 10, 2025, 10:53pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/3 "2025-03-10T22:53:05Z")

</div>

> [@bc3tech](#):
>
> PiHole creates its default **bridge** network (this is where I believe the problem is) and everything works just fine.

Pi-hole doesn't create any networks - your Docker daemon does, as per your container's configuration.

> [@bc3tech](#):
>
> I've tried setting up `macvlan` and `host` and have yet to be successful or find a working **v6 config** anywhere.

Are you running Docker on Windows or Mac?  
In that case, host or macvlan may not be available, and Docker Desktop may indeed NAT traffic to bridge mode containers.

---

<div class="post-metadata">

**Author:** ![bc3tech](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bc3tech/32/30431_2.png) [@bc3tech](https://discourse.pi-hole.net/u/bc3tech)\
**Post date:** [March 11, 2025, 1:10am UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/4 "2025-03-11T01:10:28Z")

</div>

Yes I meant the YAML used to create the container.

This setup is on a Synology NAS that previously had no problem with v5...

---

<div class="post-metadata">

**Author:** ![bc3tech](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bc3tech/32/30431_2.png) [@bc3tech](https://discourse.pi-hole.net/u/bc3tech)\
**Post date:** [March 11, 2025, 3:23pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/5 "2025-03-11T15:23:26Z")

</div>

> **No longer an issue**
>
> Appears I spoke too soon. Dashboard isn't serving anything up externally and is only reflecting internal queries from the container itself.
> 
> docker network config:
> 
> ![image](https://discourse.pi-hole.net/uploads/default/original/3X/a/6/a6591fbe27780559c6d73e8a1e50879238e3021e.png)
> 
> pihole container config:
> 
> ![image](https://discourse.pi-hole.net/uploads/default/original/3X/2/9/2994a32bde46354cd1b5111eb2382cc898f3ba04.png)  
> ![image](https://discourse.pi-hole.net/uploads/default/original/3X/4/d/4d524b63ac1318e983d012e33a2635460e4f0af9.png)
> 
> ```auto
> $ nslookup github.com 192.168.1.250
> ;; connection timed out; no servers could be reached
> 
> ```
> 
> furthermore, when the container boots, it gets errors _itself_ trying to resolve DNS:  
> ![image](https://discourse.pi-hole.net/uploads/default/original/3X/b/a/ba959cde6ecc6ea9c3d646c45f5f5feeddf5c828.png)
> 
> If I change the container to bind to a `bridge` network, I get no DNS errors from _within_ the container, but still cannot use it on the IP address I want to from outside:
> 
> ![image](https://discourse.pi-hole.net/uploads/default/original/3X/5/0/5023dd3f3d09b8d86e1b321b3ef9555cd6ab994a.png)
> 
> ```auto
> $ nslookup github.com 192.168.1.250
> ;; connection timed out; no servers could be reached
> 
> ```

---

<div class="post-metadata">

**Author:** ![bc3tech](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bc3tech/32/30431_2.png) [@bc3tech](https://discourse.pi-hole.net/u/bc3tech)\
**Post date:** [March 11, 2025, 5:56pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/6 "2025-03-11T17:56:08Z")

</div>

Have the pihole exposed now and fielding requests. Turns out my Synology has both `eth0` and `ovs_eth0` interfaces; the first one isn't bound to an IP, the second one is. Had to use that interface name.

Now, back to getting resolution working for local IPs...

---

<div class="post-metadata">

**Author:** ![bc3tech](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bc3tech/32/30431_2.png) [@bc3tech](https://discourse.pi-hole.net/u/bc3tech)\
**Post date:** [March 11, 2025, 5:58pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/7 "2025-03-11T17:58:32Z")

</div>

![image](https://discourse.pi-hole.net/uploads/default/original/3X/1/0/10e66b17cc4f61907100ca994b3b59d4bc5cb1c4.png)

What I'm after is to get that `192.168.1.152` to actually resolve to the device name.

---

<div class="post-metadata">

**Author:** ![Ladrien](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/ladrien/32/39018_2.png) [@Ladrien](https://discourse.pi-hole.net/u/Ladrien)\
**Post date:** [March 11, 2025, 6:17pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/8 "2025-03-11T18:17:54Z")

</div>

> [@bc3tech](#):
>
> What I'm after is to get that `192.168.1.152` to actually resolve to the device name.

You'll need to enable conditional forwarding in the pi-hole's DNS settings and point it to your DHCP server. Without conditional forwarding, pi-hole has no idea what hosts map to which IP.

---

<div class="post-metadata">

**Author:** ![bc3tech](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bc3tech/32/30431_2.png) [@bc3tech](https://discourse.pi-hole.net/u/bc3tech)\
**Post date:** [March 11, 2025, 9:10pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/9 "2025-03-11T21:10:29Z")

</div>

That's what I thought as well; added this conditional fwding value: `true,192.168.1.0/24,192.168.1.1`, no change - _disabled_ "never forward reverse lookups for private IPs", no change.

1.1 is my router and DHCP server

---

<div class="post-metadata">

**Author:** ![Ladrien](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/ladrien/32/39018_2.png) [@Ladrien](https://discourse.pi-hole.net/u/Ladrien)\
**Post date:** [March 11, 2025, 9:15pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/10 "2025-03-11T21:15:10Z")

</div>

Can you confirm that the pi-hole is asking your router for PTR records? You should be able to find them in the query log.

---

<div class="post-metadata">

**Author:** ![bc3tech](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bc3tech/32/30431_2.png) [@bc3tech](https://discourse.pi-hole.net/u/bc3tech)\
**Post date:** [March 11, 2025, 10:05pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/11 "2025-03-11T22:05:16Z")

</div>

Looks like it

 ![image](https://discourse.pi-hole.net/uploads/default/original/3X/f/9/f94890b4bb518013232005b973539752626a0fa0.png)

---

<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:** [March 11, 2025, 10:41pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/12 "2025-03-11T22:41:45Z")

</div>

> [@bc3tech](#):
>
> What I'm after is to get that `192.168.1.152` to actually resolve to the device name.

Let's ask your router at `192.168.1.1` if it knows a name for that IP.  
Please share the output of:

```auto
nslookup 192.168.1.152 192.168.1.1

```

---

<div class="post-metadata">

**Author:** ![bc3tech](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bc3tech/32/30431_2.png) [@bc3tech](https://discourse.pi-hole.net/u/bc3tech)\
**Post date:** [March 11, 2025, 11:00pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/13 "2025-03-11T23:00:08Z")

</div>

seems like we're honing in on something....

```auto
$ nslookup 192.168.1.152 192.168.1.1
** server can't find 152.1.168.192.in-addr.arpa: NXDOMAIN

```

My router is a Netgear Orbi 850 - I'll start researching if there's a way to enable this. Seems like might be in the same boat as others where the Router doesn't actually serve DNS requests for the local network. To me this is odd, since I can use named hosts to _get_ to places on the network.... 🤔

---

<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:** [March 11, 2025, 11:06pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/14 "2025-03-11T23:06:51Z")

</div>

Let's verify that.  
For such a named host, what's the output of:

```auto
nslookup namedhost 192.168.1.1

```

where you substitute `namedhost` with a name you expect your router to know.

---

<div class="post-metadata">

**Author:** ![bc3tech](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bc3tech/32/30431_2.png) [@bc3tech](https://discourse.pi-hole.net/u/bc3tech)\
**Post date:** [March 13, 2025, 3:06am UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/15 "2025-03-13T03:06:14Z")

</div>

```auto
>nslookup snas 192.168.1.1
Server: UnKnown
Address: 192.168.1.1

Name: snas
Address: 192.168.1.144

```

and the reverse

```auto
>nslookup 192.168.1.144 192.168.1.1
Server: UnKnown
Address: 192.168.1.1

Name: snas
Address: 192.168.1.144

```

checking if pi.hole can do the same

```auto
>nslookup 192.168.1.144 192.168.1.250
Server: pi.hole
Address: 192.168.1.250

Name: snas
Address: 192.168.1.144

```

appears it can but  
when i use `.152` (address of this PC), it gets

```auto
>nslookup 192.168.1.152 192.168.1.250
Server: pi.hole
Address: 192.168.1.250

*** pi.hole can't find 192.168.1.152: Non-existent domain

```

---

<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:** [March 13, 2025, 8:05am UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/16 "2025-03-13T08:05:17Z")

</div>

So in general, your router is capable of providing local name resolution for local hostnames as well as for reverse lookups, but fails to do so for specific IP addresses.

That would be normal for devices that have been assigned a static IP on the device itself, as those wouldn't register with your router.

The easiest way to allow them to resolve would be to create the respective [Local DNS records](http://pi.hole/admin/settings/dnsrecords) within Pi-hole.

---

<div class="post-metadata">

**Author:** ![bc3tech](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bc3tech/32/30431_2.png) [@bc3tech](https://discourse.pi-hole.net/u/bc3tech)\
**Post date:** [March 13, 2025, 2:31pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/17 "2025-03-13T14:31:46Z")

</div>

Well shoot that stinks - I have 90 devices on my network so really was hoping for something more automatic.

---

<div class="post-metadata">

**Author:** ![bc3tech](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bc3tech/32/30431_2.png) [@bc3tech](https://discourse.pi-hole.net/u/bc3tech)\
**Post date:** [March 13, 2025, 2:36pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/18 "2025-03-13T14:36:28Z")

</div>

Related question

I set my router ( `192.168.1.1` ) to have its DNS records as `192.168.1.250` (my pi.hole instance) and `1.1.1.3` (cloudflare in case the pi.hole is down/lagging).

When I look at my ph query logs, I see 99% of requests coming _from my router_ and not the individual clients. My expectation was that by setting the DNS records in my router, it would "tell" clients that connect to the router that they should be using those values as _their_ DNS. But it seems that the clients are simply asking the router for DNS and the router is asking pi.hole.

Is there a way to avoid having to _manually_ set pi.hole as the DNS server on every single device on my network but have them _directly_ hit the pi.hole so the logs show the _real_ client making the request?  
This will at least help me to start building those local DNS records by doing so right from the logs.

---

<div class="post-metadata">

**Author:** ![Ladrien](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/ladrien/32/39018_2.png) [@Ladrien](https://discourse.pi-hole.net/u/Ladrien)\
**Post date:** [March 13, 2025, 6:00pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/19 "2025-03-13T18:00:50Z")

</div>

> [@bc3tech](#):
>
> Is there a way to avoid having to _manually_ set pi.hole as the DNS server on every single device on my network but have them _directly_ hit the pi.hole so the logs show the _real_ client making the request?

If your devices are on static IPs, no. This is what DHCP is meant to do. I would ask myself if I truly need static IPs for these 90+ devices, if not, consider switching them to DHCP and all of these problems will resolve themselves.

As a rule of thumb, you generally only set servers to static IPs. All client devices get DHCP, with an optional static lease to prevent the IP from changing.

---

<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:** [March 13, 2025, 7:36pm UTC](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838/20 "2025-03-13T19:36:17Z")

</div>

> [@bc3tech](#):
>
> I have 90 devices on my network so really was hoping for something more automatic.

And you really have manually configured static IPs on each of the devices, apart from your `snas/192.168.1.144`?

Did you configure that `192.168.1.250` IP manually on the device that carries that IP? What kind of device is it?

> [@bc3tech](#):
>
> When I look at my ph query logs, I see 99% of requests coming _from my router_ and not the individual clients.

That would indicate that you have configured your router to use Pi-hole as its upstream DNS server (commonly, a WAN/Internet kind of setting), as opposed to configuring it to distribute your Pi-hole's IPv4 to its clients vai DHCP (commonly, a LAN/DHCP kind of setting).

In either configuration, DNS requests will be filtered by Pi-hole, but you only would be able to attribute DNS requests to individual clients with the latter configuration.

[Next page](https://discourse.pi-hole.net/t/vanilla-v6-install-no-local-name-resolution-in-logs/77838.md?page=2)