mrkambo

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by mrkambo

  1. 1 hour ago, jzawacki said:

    Since PiHole has the ability to track individual devices, I would configured the DHCP server to hand out 192.168.1.3 and a fake IP address for the second IP.

     

    Then, on PiHole, make it's upstream DNS custom and give it 192.168.1.4.

    Then, on LanCache server, give it's upstream DNS as your ISP's DNS or 8.8.8.8, or whoever you prefer.

     

    Using this method, you retain all the function of PiHole with the benefit of the LanCache server.  Just keep in mind that if DHCP hands out more than 192.168.1.3 as a valid IP address, things might not always work correctly, as windows doesn't use them as primary and if I can't talk to primary, use secondary, it will randomly use either of them depending on how it feels at the time.

     

    You may also have to clear the DNS cache on the PiHole if it already knows the real IP address for the services you are trying to cache.

     

    James

     

    Thanks, this worked an absolute treat......

  2. Can anyone advise on how i set this up correctly using PiHole...

    My PiHole acts as a DHCP server and DNS - Its IP is 192.168.1.3, I've given lancache the IP of 192.168.1.4

     

    Upstream in the container is 192.168.1.3 - is this correct?

     

    Im assuming that i give PiHole the IP for lancache as primary DNS and then leave local host as secondary DNS

    Any advice?