on a machine that is served by the pi-hole dhcp server (running on pi-hole not router) resolve the hostname of the pi-hole
cannot find pi-hole name - and have to use the ip directly
n3avhveuok
This site can’t be reached
pi.hole’s server IP address could not be found.
however
on the pihole itself - it said connection refused through the elinks app.....
sorry correction - it works if I use http but not if i use https direclty on the pi-hole. So the machine knows how to get to itself though the alternate name - but isn't sharing that info with the local population.
I'm a bit confused now.
Was this loading the web admin page (and if so, what address were you using) or trying to lookup pi.hole as a domain (i.e. dig pi.hole, etc.)?
The interface for the web admin page is on port 80 (http) and not on port 443 (https).
well it is 1/2 working now - although I have had this DNS / DHCP server in place for a while now at least my linux boxen are resolving it locally. I don't know why my windows machines are not though - even with a flushdns - but I can live with that.....
This thread may have some additional information:
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.