OPNsense Forum

Archive => 20.7 Legacy Series => Topic started by: bignick8t3 on January 31, 2021, 01:01:25 pm

Title: Captive Portal DNS [SOLVED]
Post by: bignick8t3 on January 31, 2021, 01:01:25 pm

Hi All,

Last week I setup a Captive Portal for my guest network, I used the following for guidance:
https://docs.opnsense.org/manual/how-tos/guestnet.html

Everything worked out great and I was able to get this working while the guest network was using the DNS (Unbound) of OPNsense.

With all my networks/vlan's DNS is usually by the following process:

Client - Pi-hole DNS - OPNsense (Unbound)

So the DHCP on OPNsense hands out the Pi-hole address which then queries OPNsense for anything it cannot answer.
In turn I have the required firewall rules for this to work.

When I do this for the guest network using the Captive Portal the portal won't load and any device that connects just comes up with no internet access.

I have confirmed that the Pi-hole can resolve the name used within the Captive Portal settings and I amend any firewall rules to match what I'm trying to do.

Any guidance on to where I am going wrong at all?

Thanks,

Nick

Title: Re: Captive Portal DNS
Post by: bignick8t3 on February 03, 2021, 02:08:31 pm

I found the issue on this one.

I needed to add my DNS servers to the "Allowed Addresses" within the Captive Portal settings.
This wasn't obvious to me but problem solved.

Nick

Title: Re: Captive Portal DNS [SOLVED]
Post by: talanda on November 19, 2021, 03:05:05 pm

I had the same problem. Thanks for sharing solution.