@TP-Link Some of your wording doesn't make much sennse to me. Intruige?

 

Can you take a look at my settings screens and tell me if that will work given the subnet masks / conflicts / etc? I feel like I'm being told to chase my tail... I've outlined my network config and sample IPs, and have asked if those settings will solve the "rare" issue you have brought up. So... will it?

@TP-Link Great! I will test right now...

 

But won't any device on the WAN not use piHole? Or does the deco somehow reoute WAN DNS requests to the LAN DNS servers?

@TP-Link Well, none of the wireless devices are using the piHole so I need to keep trying. The wired devices are usingthe piHole for DNS, so that's good and we'll see if it changes the subnet mask....

 

I guess this means I need to try SOLUTION #2. correct? You're saying If I have the same subnet masks for WAN and LAN, there won't be any IP conflict for 192.168.0.229, is that correct? How does that work, and how do I implement it?

 

My other thought was to have two network adapters on the piHole, the eth0 (wired & LAN) and then a wlan0 (wireless & WAN). Not sure if a raspberry pi can even do this.

Also, is there perhaps a SOLUTION #3 - make a second piHole device, and put it on the WAN, and then put THAT ip in the IPv$ (WAV) settings screen?

 

I feel like I'm getting close, but still don't get why I can't use the piHole IP on the WAN. Seems like Tp-Link / Deco could figure out an internal way around this since it is a pretty common configuration... But admittedly, I don't know much about netsec, so maybe there's good reason behind it.

 

Appreciate your help

@TP-Link I can't figure it out. The only devices using piHole are the hard wired (LAN) devices.

 

The good news is that my mask / IPs aren't changing, but what's the point of using piHole / a custom DNS provider if more than half of the devices on my network can't access it - So the WAN DNS can't be the same as the LAN DNS...

 

What do I do at this point?

 

How do I configure the WAN's DNS servers to point to my piHole?

 

Do I need to configure some sort of redirect / table?

@TP-Link just a friendly follow up. Did you see my last two messages? I can get PiHole working as a DNS server on the LAN, but not on WAN which makes it pointless. I have tried using a second IP address on a different subnet mask (192.168.1.229) but that doesn't seem to work either. So... is there a fix for this? Or are you saying I need to hire an netsec / IT specialist to somehow set up a second network so my WAN devices can use a local DNS server?