The pihole.log
shows lots of devices successfully got their DHCP lease from Pi-hole "DHCPACK
".
So the Galaxy device with IP 10.1.1.246
should have no problems browsing to http://pi.hole/admin ?
I dont know how to troubleshoot a Chromebook I must say.
Your Ubuntu client probably runs its own forwarding DNS service for caching.
Thats why querying with nslookup
defaults to querying the address 127.0.0.53
on the internal loopback interface as configured in /etc/resolv.conf
.
To figure out who is listening on that 127.0.0.53
IP address on DNS ports 53 UDP & TCP, you could run below on the Ubuntu client (netstat
being part of net-tools
package):
sudo apt install net-tools
sudo netstat -nltup | grep 'Proto\|:53 '
If lucky, below one on the Ubuntu client will show what upstream DNS servers are configured on the client (dig
being part of dnsutils
package):
sudo apt install dnsutils
dig +short chaos txt servers.bind
You can check the systemd
journals on the Ubuntu client but try do this right after a client reboot:
sudo journalctl -x --no-pager | grep -i dhcp | tail -15
Or run below on the Ubuntu client to renew/confirm DHCP lease and show verbose output:
sudo dhclient -v
And I believe you still have nmap
installed on that Ubuntu client right ?
sudo apt install nmap
What does below show on the Ubuntu client ?
sudo nmap --script broadcast-dhcp-discover
sudo nmap -sU -p67 --script dhcp-discover 10.1.1.1
sudo nmap -sU -p67 --script dhcp-discover 10.1.1.3
Ps. above should all be done while Pi-hole is configured to do DHCP for your network!