Pihole in a docker container don't resolve local ips

Help Community Help
1

I have a fritz 192.168.188.1 as dhcp and a docker container on a linux server 192.168.188.100 with casaos.

Pihole works wery well, but when from any of my local client i try to ping another pc, also the 188.100, i receive every time the same answer with the same wrong ip:

nslookup lnxsrv.fritz.box
Server: 192.168.188.100
Address: 192.168.188.100#53

Non-authoritative answer:
Name: lnxsrv.fritz.box
Address: 45.76.93.104

i tryed to dig from fritzbox router:
dig 192.168.188.1 +short lnxsrv.fritz.box
192.168.188.100

That's correct... and after from pihole host:
dig 192.168.188.100 +short lnxsrv.fritz.box
45.76.93.104

:weary:

But EVERY client digged from 188.100 retreive the same ip:
dig 192.168.188.100 +short MBP-di-Loris.fritz.box
45.76.93.104

Also the fritz router from 188.100 retreive the same ip:
dig 192.168.188.100 +short fritz.box
45.76.93.104

I can't understand whats going on.

Can some one help a noob like me?
Thanks!

2

On your 192.168.188.100 Linux server, what's the result of:

cat /etc/resolv.conf
1 Like
3

cat /etc/resolv.conf
domain fritz.box
search fritz.box
#nameserver 1.1.1.1
#nameserver 1.0.0.1
nameserver 192.168.188.1

This is from 192.168.188.100, would you like also the resolv.con from the docker container?

FYI the docker container in not on the same lan (i don't know why)
This is it's ip:
eth0@if20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:ac:12:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 172.18.0.2/16 brd 172.18.255.255 scope global eth0
valid_lft forever preferred_lft forever

4

That output looks inconspicous.

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

5

Your debug token is: https://tricorder.pi-hole.net/BkxPcb6L/
Thanks!

9

Your Pi-hole is passing that request to its upstreams, and recently, the public fritz.box domain has come into owership by some obscure third-party, not by AVM (the manufacterer of FritzBox routers, see also Pi-Hole server only reachable by IP - #6 by Bucking_Horn).

Your debug log shows you've enabled Pi-hole's Conditional Forwarding via Settings | DNS, but didn't state a domain.

You have to add fritz.box as local domain.

Pi-hole would then forward your request to your FritzBox router, which would provide the correct answer.

2 Likes
10

Thanks very much, but where i have to add fritz.box as local domain, in pihole or in my fritz router settings?

11

In Pi-hole, as mentioned already:

12

Yes yes sorry, i understand too later :stuck_out_tongue:
I'm going to try...

13

Works like a sharm!
Thanks very much! :star_struck:

14

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