I created a VLAN (192.168.200.1) for testing so I can assign VPN user to that network. The untagged network is at 192.168.0.1. PiHole IP is 192.168.0.9.
For the VLAN, I set DNS Server1 to 192.168.0.9. With this setting VPN user can reach devices on the untagged network but cannot browse the web. If I set DNS Server1 to 8.8.8.8, I can browse the web but not have the use of pihole ad-blocking. What am I missing?
We have a bunch of PiHoles out there and they work extremely well. I’m guessing when you say “cannot browse the web” that you mean DNS resolution fails. And you don’t say which device you are using and how the clients are connected. One thing to check is that access to the local network is not being restricted (as below.) And, just as a sanity check, make certain you can ping the pi from both the untagged and VLAN segments.
@Laurynas
The pihole setup works in the 192.168.0.1 network. All devices can browse the web with working adblocking.
@Rick-DC
You are correct on the DNS resolution failing. I did miss the important detail of client connection. The client connects via OpenVPN into the Balance20.
I can ping the pihole and access the pihole admin from the client device in the vlan. Let me know if other details needed. Thank you for the assist.
Just tested this with my setup, and can confirm that remote user through OpenVPN with PIhole’s set as DNS will allow me to browse the web with no issues.
You are only adjusting the “Remote user” VLAN DNS not the untagged one right?
Additionally, in the pihole settings under DNS, I have found that I have had to adjust the interface settings to “permit all origins” for stuff to work correctly.
Thank you! I think you nailed the issue. I will try the change and report back as soon as I figure out why my pihole setup won’t let me save settings.