DNSFilter Roaming Client Conflict with Public Wifi
Answered
Hello,
We allocate 10.11.0.0/24 as a locally used subnet. Our devices are installed with the DNSFilter Roaming Client.
We have one particular public wifi network in a local court system that utilizes 10.11.187.0/20 as their allocated DHCP range for this network. They have a captive portal that needs to be resolved which fails to do so.
DNSFilter Roaming Client seems to conflict with this although it falls outside of our 10.11.0.0/24 subnet. It seems like the Roaming Client “assigns” the entire 10.0.0.0/8 to our local resolvers for some reason. Uninstalling the Roaming Client allows access to the captive portal. Is there any way around this?
The only thing I can see is local domains which would be unhelpful as we are not trying route their DNS lookups to our on prem resources.
-
Official comment
Wanted to post a quick update here, as the team was able to solve the issue. Captive Portal was the culprit: adding the root domain to the Local Domains list restored access.
Glad the team was able to help, and feel free to reach out again if anything comes up!
-
Hi Jameson Perham , thanks for reaching out! What you're describing seems related to the Captive Portal more than the subnet setup, but our team would like to see diagnostic logs from an impacted device to confirm.
I'm going to start a ticket related to this post—you'll receive notification shortly—and please reproduce the issue, collect logs, and attach them to a reply to that ticket for our team to investigate.
0
Please sign in to leave a comment.
Comments
2 comments