I'm using the DHCP server on my router, not the Pi Hole, but I really don't understand how the above can be happening. host resolves the name to the correct IP address, I can ping the IP address, but if I ping the hostname it doesn't resolve?! That doesn't make any sense.
(Everything else works fine from the machine I'm attempting to send the ping from.)
And whaddayaknow, I just tried ping pi.hole again and it worked!
mella:~ ratkins$ ping pi.hole
PING pi.hole (192.168.1.2): 56 data bytes
64 bytes from 192.168.1.2: icmp_seq=0 ttl=64 time=146.118 ms
64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=192.368 ms
64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=1.151 ms
^C
--- pi.hole ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.151/113.212/192.368/81.458 ms
This is extremely odd. I guess something was cached somewhere and had to expire (I had changed the IP of the Pi Hole from .42 to .2 in the hours before I first posted.)
Sorry for the false alarm, but I promise the above output is cut and pasted directly from my terminal without me fiddling with it .
You have 1.1.1.1 as a nameserver listed. There isn't a "secondary" or "fallback" DNS server, both the listed servers will be used. When you ping and the name lookup fails that is because the client is asking 1.1.1.1 for the name instead of asking 192.168.1.2. 1.1.1.1 doesn't know pi.hole so it fails.