I have a work laptop that I bring between work and home as some of my work is done remotely from home. When connected to my network it just hammers the DNS server (PiHole) with reverse DNS lookup requests for IP addresses that aren't even on my network (My network is using a 172... subnet).
These happen quite fast and very consistently at at least 1 every 4-10 seconds sometimes with multiple queries at the same time.
You can see the large dip during the day when I bring the laptop to work, and spike back up when I bring it back home. According to the dashboard, over 1/3 of all queries are PTR queries...
The hardware is more than capable of handling it, but it makes the logs really messy if I'm looking for anything since I have to sift through all these entries that I don't care about. I don't really care if it does it in the background, I just don't want to see it.
Is there any way I can completely exclude only this one device from PiHole and logs?
Things I've tried/considered:
-
Group Settings
I tried making a separate group and adding the work computer to it. However while PiHole's group settings allow me to change what filters/black/whitelists are applied to a given device, the device still uses PiHole and the queries still show up in the logs -
Setting ANALYZE_ONLY_A_AND_AAAA
I tried settingANALYZE_ONLY_A_AND_AAAA
toTrue
in the PiHole settings, which does cause all the PTR/reverse DNS queries (and some other query types it does) to not appear in the logs.
However when I do that, I find that there are ads that get through using something besides A or AAAA and when I set it back toFalse
the ads no longer appear. So I would like to leave this set toFalse
so that those ads remain blocked given the whole purpose of this is to block ads -
DNS Settings on the Computer
One obvious way that would make sense to exclude it from the PiHole would be to change it's settings to not point at the PiHole as it's DNS server.
Unfortunately, as the machine is a work-managed computer, I don't have admin access to change settings including the DNS settings. So anything I can do will have to be done from the PiHole side.