I don’t think anyone said that Apple is enforcing their dns per say. The point was to enforce the use of your own designated dns inside your network/wifi. You don’t want to ask your friends and family go through that list to disable Apples DNS. Wouldn’t be long before they’d get you hospitalized at the nearest crazy house😀
Oops, I understood you meant that Apple enforces something. I think first @sotix needs to figure out which setting is causing this problem and then it might be clearer what could be wrong with unbound + adblock setup. Point #1 is already ruled out. Bonus point as well. 4 more to check.
As far as I'm aware, everything is set up correctly on my Apple devices to disable each of the things listed, and the DNS is set to Automatic. I seem to be compliant with your list.
The most likely issue is how I set my DNS up because that's where I'm not an expert. But I can't figure out why it works on every non-Apple device. I don't think that's a coincidence.
It would help us if you showed the DNSs that are being leaked to when you used the link.
An since you have a pi-hole around, update Gravity and test the Pi-hole after that.
Post both results unless they are identical.
But close port 53 when using the pi-hole and have all devices use dhcp from the router and set the custom DNS to the pi-hole's address.
Both results are identical, so I think that means it's working! I'm not sure what exactly did it since I changed a few things, but I think adding port forwarding for 53 and rebooting all of the devices got things in alignment. Thanks for all of the help!
1 Like
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.