Getting client information on docker, behind Edgerouter (dhcp) and Fritzbox

Help Community Help
1

Hi all,

I know this is a well known issue, but I can't get it to work somehow...
I have Pi-hole running in docker container, my full network setup looks like this:

  • Fritzbox from my provider
    DHCP in the 192.168.178.x range
  • Edgerouter X
    Only device to get IP from Fritzbox, has DHCP server in 192.168.1.x range with 192.168.1.1 as it's own
  • Proxmox device with a virtual machine (fixed IP)
    • Virtual machine is running docker container with Pi-Hole

In EdgeOS DHCP settings, the IP of the virtual machine is set as DNS server.

Pi-Hole is working fine, in my 'top clients' list I see different local IP addresses from clients.
But I can't add clients to groups, the 'known clients' list only shows the options

  • 0
  • success
  • message (Error while querying FTL's database: not an error)

The list of configured clients keeps saying 'loading...'.

At settings -> DNS I enabled 'Use conditional forwarding', with local network 192.168.1.0/24 and DHCP ip 192.168.1.1.

Am I missing something?

Should I try to have the fritzbox and the ER on the same network range? (I got the FB later and had trouble with it to change it to my range)

2

Let's check whether your EdgeX would run a DNS resolver that knows local names:

nslookup 192.168.1.1 192.168.1.1
3

UnKnown can't find 192.168.1.1: Non-existent domain

or

server can't find 1.1.168.192.in-addr.arpa: NXDOMAIN

4

Just to be sure, also run a lookup for a local name of one if your clients, e.g.

nslookup laptop 192.168.1.1

Substitute laptop as appropriate.

And just curious: Why two different results? Different clients?

5

Same results:

server can't find a-local-name: NXDOMAIN

Yes, one is on the docker container itself, other is on my windows laptop

6

I've used laptop as an example.
Is that indeed one of your hostnames?

7

Yes, I've tried two different hostnames

8

That would demonstrate that your Edge router X (like many Ubiquiti models) does not know local names.
In some models, you may be able to replace the router's DHCP server with dnsmasq, in order to correctly supply names for Pi-hole's Conditional Forwarding requests.

This should also allow Pi-hole to populate the client list at least with hostnames.

You should consult Ubiquiti's documentation and support for instructions (our forums may also have posts that link to them).

9

Thanks!
Changed to dnsmasq, now the nslookups are working and the Top Clients list shows hostnames indeed.

But the 'known clients' list on the Clients page was still the same.
Had to make a new query database, all looks ok now!

10

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