Support on very scenario
Hello, my usecase is simple.
I want to block a specific website in my home wifi, and testing out first the scenario on my own Mac.
1) The policy has been created, and I only filled in the tab “Block List” to add the website domain and the category
2) On Deployments→Sites, I assigned the policy to the network
3) I added the 103.247.36.36 and 103.247.37.37 IPs to my Mac's DNS settings
4) on https://debug.dnsfilter.com, everything is green
5) website is not blocked.
Can you let me know what further checks I can do?
-
Thanks for reaching out! Here are 3 initial troubleshooting steps to try:
- If you only blocked a single website, the debug page should show all green: it tests Category Blocks, not Allow/Block list entries. To test if the individual page is blocked you'll need to attempt to navigate to the site (try incognito mode or clearing your cache first, too).
- Confirm transparent proxying is not taking place. Run the DNS Leak Test from this article to confirm your ISP isn't intercepting DNS traffic.
- If you're able to confirm traffic is not proxied, you may need to block multiple domains in order to stop access. Use the Query Log to determine any additional domains to block in order to limit access.
Let us know if this resolves the issue, and if not happy to keep investigating!
0 -
Hey!
Thanks for your quick feedback.
Now:
I retried everything again, with cache emptied + incognito
1) Private Relay on my iCloud isn’t working anymore. I would have hoped for a solution that only filters websites,
But doesn’t impact anything else. Would that be possible?
I understand there’s limitation as well in terms of ipv4? I would like to avoid needing to operate on each local machine separately
2) I cannot access any other website than anything on the DNSFilter domain (all config pages, your home page, etc.)
3) the website I want to block is correctly blocked, somehow
4) the leak test does work as well, and shows a dnsfilter.com domain properly. Not sure why their domain also works.
Any other lead?
Best,
Kim0 -
Hi Kim, let's keep trying!
- Apple's Private Relay is blocked by design if a Roaming Client is deployed because the setting interferes with proxy extensions like DNSFilter that intercept DNS traffic. If you're seeing it not functioning on your Wi-Fi network deployment that should not be happening, so we'll want to look further into that if it's the case.
- If you tested the deployment on your device settings following this article you may've forgotten to reverse course and remove the settings. Once you remove them you should be back online and able to direct DNS traffic to DNSFilter from your firewall or router.
- DNSFilter domains are exempt from being blocked by our services so in the case something happens admins always have access to the configuration to fix the issue.
Could you provide more details about your question about IPv4 support? On a high level IPv4 is fully supported, but IPv6 has limitations.
Once we have more detail we should be able to get you all set up. You may also be interested in our Onboarding Webinars—the next one is this Thursday!
0 -
Hey Minetta,
I think we misunderstood each other:
1-2. I'm still only testing on my local machine. As it didn't work there of course I didn't put it on my router yet. Do you have other ideas on how to solve the issue locally first?
It's my confusion here: yes I meant IPV6. But my concern is the same: If IPV6 is not supported, it means that i have to adapt all of my devices? Or it will still be able to connect normally?
Thx :)0 -
Hi Kim! I'm totally stumped about why you're getting completely blocked on your individual device, so am going to create a support ticket for you from this post so the team can dig in a little more with you. You'll be in good hands!
You'll receive a notification shortly, and if you could reply to the ticket thread with your current IP address (whatismyipaddress is an easy resource to confirm) and a screenshot of your local machine's DNS Settings that should get you rolling in a good direction.
0
Please sign in to leave a comment.
Comments
5 comments