I am not sure but I think I saw somewhere you need to set your pi hole as the DHCP server in order successfully resolve your local DNS entries, can’t remember where.
Well, your Guest Wi-Fi can either have access to the pihole server and have its benefits, or point them to a public DNS. You can’t block access to the dns server for your guest network and hope it works - because it’s blocked. Personally I’d give Guest Wi-Fi a public DNS, as you won’t have much fun when an app of your friend’s stop working and you have to fiddle and work it out.
If you point the guest network’s dns to the gateway, that gateway needs to know what to do with those requests. Either it has a resolver locally or it mist forward it elsewhere.
If you point the guest network’s dns to the gateway, that gateway needs to know what to do with those requests. Either it has a resolver locally or it mist forward it elsewhere.
Yep, you’re correct, and that’s working as expected except for Pi Hole Local DNS entries.
I’ve configured DNS in DHCP to the Gateway and I can successfully access the internet on my Guest WiFi network. It resolves ALL DNS entries correctly, except for Local DNS entries configured in Pi Hole.
Depending on the hardware, you could totally allow access to port 53 via a firewall rule. Unifi does this transparently if you configure a DNS server running on a vlan other than the one you’re connected to.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Do you have conditional forwarding enabled in pihole settings? I think you need that.
Thanks, tried that, but didn’t make a difference.
I am not sure but I think I saw somewhere you need to set your pi hole as the DHCP server in order successfully resolve your local DNS entries, can’t remember where.
Well, your Guest Wi-Fi can either have access to the pihole server and have its benefits, or point them to a public DNS. You can’t block access to the dns server for your guest network and hope it works - because it’s blocked. Personally I’d give Guest Wi-Fi a public DNS, as you won’t have much fun when an app of your friend’s stop working and you have to fiddle and work it out.
If you point the guest network’s dns to the gateway, that gateway needs to know what to do with those requests. Either it has a resolver locally or it mist forward it elsewhere.
Yep, you’re correct, and that’s working as expected except for Pi Hole Local DNS entries. I’ve configured DNS in DHCP to the Gateway and I can successfully access the internet on my Guest WiFi network. It resolves ALL DNS entries correctly, except for Local DNS entries configured in Pi Hole.
Depending on the hardware, you could totally allow access to port 53 via a firewall rule. Unifi does this transparently if you configure a DNS server running on a vlan other than the one you’re connected to.
My router is very basic, so it’s all or nothing, i.e. can’t configure VLAN or firewall rules.