I just installed OpenWrt on my TP-Link Archer C7 router, which seems to be working fine. I can access the internet from various devices and have static IPs setup for some (but not all) of them, including the "Pi-Hole device" which is a Xiaomi Mi A2 Lite running Debian Buster via Linux Deploy. I also have OpenWrt configured to use the Pi-Hole's IP address (192.168.1.10) as the only DNS server, and this seems to give me reliable ad blocking from at least one device (a Windows laptop).
The only problem is that the admin query log and any other FTL-related stat pages are unavailable, and while I don't really need to be able to use "pi.hole" instead of the IP, it would be nice to be able to do so.
If you guys need any more info, please don't hesitate to ask. MTIA!
@DanSchaper Thanks for the quick reply! After connecting to the phone over SSH using my laptop and running your suggested command, I get the following:
; <<>> DiG 9.11.5-P4-5.1-Debian <<>> pi.hole @192.168.1.10
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27362
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;pi.hole. IN A
;; ANSWER SECTION:
pi.hole. 2 IN A 192.168.1.10
;; Query time: 1 msec
;; SERVER: 192.168.1.10#53(192.168.1.10)
;; WHEN: Sun Jan 26 12:43:12 AEDT 2020
;; MSG SIZE rcvd: 52
Should I try the same from another device? If so, could you please suggest a dig-equivalent command on Windows?
Just realised I hadn't exited the SSH session before running nslookup lol. So here are the results of nslookup pi.hole from both my laptop and phone, using no server, the phone's IP and the router's IP (192.168.1.1):
C:\WINDOWS\system32>nslookup pi.hole
Server: OpenWrt.lan
Address: 192.168.1.1
Name: pi.hole
Address: fdf9:7e26:4fe2:0:e98:38ff:fef3:c1e3
C:\WINDOWS\system32>nslookup pi.hole 192.168.1.10
Server: localhost
Address: 192.168.1.10
Name: pi.hole
Addresses: fdf9:7e26:4fe2:0:e98:38ff:fef3:c1e3
192.168.1.10
C:\WINDOWS\system32>nslookup pi.hole 192.168.1.1
Server: OpenWrt.lan
Address: 192.168.1.1
Name: pi.hole
Address: fdf9:7e26:4fe2:0:e98:38ff:fef3:c1e3
C:\WINDOWS\system32>ssh android@192.168.1.10
Linux localhost 3.18.120-perf-g0e12ed5 #1 SMP PREEMPT Mon Dec 9 17:53:53 WIB 2019 aarch64
Debian GNU/Linux 10 (buster) [running via Linux Deploy]
Last login: Sun Jan 26 12:43:03 2020 from 192.168.1.2
Linux localhost 3.18.120-perf-g0e12ed5 #1 SMP PREEMPT Mon Dec 9 17:53:53 WIB 2019 aarch64
Debian GNU/Linux 10 (buster) [running via Linux Deploy]
Last login: Sun Jan 26 12:43:03 2020 from 192.168.1.2
android@localhost:~$ nslookup pi.hole
Server: 127.0.0.1
Address: 127.0.0.1#53
Name: pi.hole
Address: 192.168.1.10
Name: pi.hole
Address: fdf9:7e26:4fe2:0:e98:38ff:fef3:c1e3
android@localhost:~$ nslookup pi.hole 192.168.1.10
Server: 192.168.1.10
Address: 192.168.1.10#53
Name: pi.hole
Address: 192.168.1.10
Name: pi.hole
Address: fdf9:7e26:4fe2:0:e98:38ff:fef3:c1e3
android@localhost:~$ nslookup pi.hole 192.168.1.1
;; connection timed out; no servers could be reached
I find it very interesting that the phone can't reach the router; what does this mean??
