Could you also run that dig via your router, probably @192.168.178.1?
And also, 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
Debian GNU/Linux 11 (bullseye) [exactly Debian V11.6]
Is that the lite version (minimal install) or does it come with a desktop?
EDIT: Could you post the download link or similar?
Command: dig -x 192.168.178.25 @192.168.178.1
; <<>> DiG 9.16.37-Debian <<>> -x 192.168.178.25 @192.168.178.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15671
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
;; QUESTION SECTION:
;25.178.168.192.in-addr.arpa. IN PTR
;; ANSWER SECTION:
25.178.168.192.in-addr.arpa. 9 IN PTR Galaxy-A21s.fritz.box.
;; AUTHORITY SECTION:
25.178.168.192.in-addr.arpa. 9 IN NS fritz.box.
;; ADDITIONAL SECTION:
fritz.box. 9 IN A 192.168.178.1
;; Query time: 0 msec
;; SERVER: 192.168.178.1#53(192.168.178.1)
;; WHEN: Tue Mar 07 21:37:26 CET 2023
;; MSG SIZE rcvd: 110
ypS1FcCO
yes, it is the lite version without desktop.
I downloaded it from here [.iso file] and wrote it to a USB stick with Rufus [rufus.ie] and installed Debian from it:
https://www.debian.org/download
Blast, I have all sorts of Debian releases running but not the Bullseye lite release yet.
How did you configure networking like hostname and IP etc?
Did you do it the old fashioned way in /etc/network/interfaces ?
Usually if you have 127.0.0.1 or similar in resolv.conf, it would mean you have a stub resolver running for caching.
Bucking_Horn would be able to see in the debug report.
I have not done anything in /etc/network/interfaces and the resolve.conf file has 192.168.178.27 [PiHole] as the nameserver, yes.
Thank you.
Your debug log shows that your Pi-hole is neither using your FritzBox as its sole upstream, nor is Conditional Forwarding enabled, nor is it acting as DHCP server, nor are there any local DNS records.
Therefore, your Pi-hole has no means of knowing about local hostnames.
You would have to opt for any of the above (or a combination) to see local hostnames.
For now, easiest would be to point your Pi-hole to just your FritzBox, and configure your FritzBox upstreams to 1.1.1.1 and 1.0.0.1 (via Internet|Zugangsdaten|DNS Server).
In that configuration, also make sure that Never forward non-FQDN A and AAAA queries as well as Never forward reverse lookups for private IP ranges are unticked.
Please correct me, but AFAIAAO, Debian *.isos are net installation images, i.e. they prompt you for packages to install during initial installation.
As I've alluded to previously: Would you remember which networking tools you picked? Perhaps you have missed to install a tool for managing resolv.conf?
The link you provided suggests a certain such package:
From your debug, your current resolv.conf is missing the tell-tale generated by comment from resolvconf, and it also still points to Pi-hole:
*** [ DIAGNOSING ]: contents of /etc
lrwxrwxrwx 1 root root 29 7. Mär 19:29 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
nameserver 192.168.178.27
search fritz.box
That would suggest that resolvconf still isn't active.
Did you actually try to install that package?
thats right
okay, i can do that. until now i had pihole directly using 1.1.1.1 as upstream dns server. i will now set it up so that it uses the fritzbox as upstream and the fritzbox then uses 1.1.1.1.
how do i do that?
thats right. my .iso file is only 300mb
i did not select any network packages during installation, but i have now manually installed one. resolvconf.
now there is also something in /etc/resolv.conf, namely the following:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "resolvectl status" to see details about the actual nameservers.
so i can work with this now. i found instructions on the internet to use this. so now i know how to add nameservers to resolv.conf and have them stay..
yeah! it works! thank you so much!
i reinstalled the pihole and set the upstream dns to the router and set the dns server in the router to 1.1.1.1. + Never forward non-FQDN A and AAAA queries and Never forward reverse lookups for private IP ranges disabled. now everything works. everything is filtered and i see the hostnames.
thank you! thank you for pihole and this support.
thank you really!
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.