srch

As such pihole stats aren't granular by device but just lumped under the router IP. When I looked at the pihole dashboard the number of DNS ...

Step 2: Redirect DNS traffic that is neither to nor from the PiHole, to the PiHole. This code snippet assumes your raspberry pi’s IP address is 192.168.88.3, change the code below to the IP address of your PiHole instances’ address …

Hello kids! I've got Cox Communications cable Internet, my own SB6190 modem, and a Ubiquiti USG router. I FINALLY setup my own Pi-Hole.

Nothing in hosts, resolv.conf or anywhere to suggest pi.hole is what should be assumed as the domain name, yet if i ping pi.network.home, it says. PING pi.network.home (10.0.0.1) 56 (84) bytes of data. 64 bytes from pi.hole (10.0.0.1):icmp_sec=1 blah blah. Now, this only happens from the pi-hole itself and not my other devices.

I have Oneplus 5T with hardcoded 8.8.8.8 secondary DNS. I setup the PiVPN to go through my pihole. This setup is fine for home wifi, as I just used NAT on my edgerouter x to bypass the hardcoded DNS.

If a device would contact DNS servers by hardcoded IP addresses, there wouldn't be any DNS resolution involved. Neither Pi-hole nor the machine hosting Pi-hole ...

03.08.2019 · I think the pi-hole development team should reallystart planning for a world where more and more clients and devices are hard-coding DNS IPs, and the pi-hole must become a router for all network traffic to work. Routers …

Help needed: forcing hardcoded dns into pi using TPlink port forward I have the DHCP server set up, most devices give up and use the pihole checking the traffic but some seem to be running around it. Using an TP-LINK Archer AX21 UI, I want to make the hardcoded dns of my smart tv default back to my pihole.

351 votes, 130 comments. 126k members in the pihole community. "The Pi-hole® is a DNS sinkhole that protects your devices from unwanted content" …

Hardcoded DNS servers will still resolve and allow ads and tracking unless we use NAT rules that will redirect all DNS requests, no matter where they go, ...

I’m having trouble forcing hardcoded DNS to my pihole at 198.162.1.4. I have 2 VLAN’s 107 for IOT (Rokus are excluded until I can get SSDP broadcasts working for remotes and casting) 1 for everything else (I plan on creating a management VLAN as my next step once I get this working) Static IP’s 192.168.1.4 Pihole 192.168.1.8 PC 192.168.1 ...

Can someone help with Hardcoded DNS redirects on Ubiquiti Unifi I have PiHole set up, but some devices are ignoring it and going straight out to Google’s DNS. I want to stop that, and redirect those things to the PiHole.

My one remaining issue is that I have a separate IoT VLAN, and with my current config file, any DNS requests coming from that VLAN appear to the PiHole as if ...

A device using a hard coded DNS is sending DNS to some random IP on the internet outside your LAN. DHCP in no way prevents this. If a device is NOT using a hardcoded IP address, then DHCP will tell the device what DNS address to use which is your pihole assuming you have everything setup correctly.

We found numerous devices and mobile apps evade Pi-hole and other DNS ... is to hardcode DNS lookups so that they always resolve through Google's servers.

Are you running Pi-Hole and want to ensure all devices on your network use it? Find out how with a Ubiquiti EdgeRouter.

Devices with hard coded DNS will fall back to your network settings if they can't take their first preference. The reasons I like this more: You'll get Pi Hole logs telling you which device is actually making the requests (using NAT reflection makes it look like your router is making the requests.

... simple firewall rules, you can intercept these hardcoded DNS queries and redirect them to your PiHole.