Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
Expected behavior:
Hello everyone, everything good?
I am having problems with my Pi-Hole to resolve the local addresses of my hosts, on my local network.
Pi-Hole blocking has worked satisfactorily on all hosts on my local network, however, to access my hosts by name, it doesn't work properly - I'll try to put some prints in the sequence, explaining ...
- At the moment, I am using Debian 10 on my Orange Pi PC.
Let's go to the reports:
First, I must say that I configured the OrangePI PC with the hostname "thor", using the "armbian-config" tool and fixed the IP address 192.168.1.254.
When I try to access it from the pc, typing http: // thor / admin, it just doesn't work ... but if I type http: //pi.hole/admin, it works normally, follow the related prints:
When I try to access it through my phone's browser, both addresses (http: // thor / admin or http: //pi.hole/admin) work without problems, follow the related prints.
The same problem of access by the pc, I have to access my tp-link routers. I have 3 of them, the first (I call it poseidon, and has IP 192.168.1.1), connects on the internet and the other 2 (the zeus, IP 192.168.1.2 and hades, IP 192.168.1.3) are just configured as "DUMB AP" and they all run Openwrt version 18.07.2 ...
The main router has the dnsmasq and odhcpd services stopped, as I am using dhcp in Pi-Hole.
Still in Pi-Hole, I registered these hosts in Local DNS Records, but it did not have the desired effect.
I send some prints for analysis ...
Nslookup tests from Windows PC:
Putty errors call host "thor" and access Ok on host "pi.hole":
armbian-config tool setting "thor" hostname:
"dig" test 01 - Yes, I´m running unbound here!
"dig" test 02 - See the hostname...
The output of the "local.list" file:
root@thor:/etc/pihole# cat local.list
192.168.1.254 thor
fd1e:6a5f:50e3:0:11ff:8f7:2414:6508 thor
192.168.1.254 pi.hole
fd1e:6a5f:50e3:0:11ff:8f7:2414:6508 pi.hole
The output of the "custom.list" file:
root@thor:/etc/pihole# cat custom.list
192.168.1.1 poseidon
192.168.1.2 zeus
192.168.1.3 hades
192.168.1.5 an4
192.168.1.254 thor
The output of "resolv.conf" file:
root@thor:/# cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 127.0.0.1
Sorry for my english... cheers from Brazil!!