Have discovered something interesting with the DHCP server now:
Devices will not get addresses automatically from DHCP, but if I manually configure the device to have the same IP as the reservation, then things tend to be fine. Still can't get anything to resolve through the PiHole in less than 30 seconds though, but gravity is still updating.
No rogue DHCP servers, I'll have to see how I can do that probe (this is already stretching my skillset and knowledge).
I figured that the PiHole DHCP solution would 'just work' but its been a lot of trouble. I suppose I can turn it off and go back to having the ORBI handle DHCP and I'll just live without granular device logging (which was really helpful to fine tune getting ads blocked and white lists correct).
I still can't get the RPi to reliably respond to a ping, so I guess its no surprise that DHCP is failing.
In other news, looks like gravity failed to update because the PiHole can't update the lists. Any idea what would prevent PiHole itself from getting online now?
I could not generate this from the RPi directly, since it could not get online, but I was able to connect from another machine on the network, which I have configured to use a regular DNS server, bypassing the PiHole.
I suppose I need to figure out how to get more ads blocked without adding such a massive list. Still can't ping the Pi to get anything back, but at least it seems to be partially working.
Well said. I will watch how things work with the default list (when I was using the defaults I was getting a good amount of ads, but maybe I didn't stick with it long enough before adding 'more').