Q: Frustrating DNS problem - works with Chrome, not with Safari
Hello --
I use a paid DNS service that is authenticated by my IP address. In my network settings, I add the IP address of this DNS server, and it works fine in Chrome.
My DNS list looks like this:
[custom DNS IP]
192.168.1.1
Chrome uses the custom DNS with no problems -- I know this because this DNS service allows me to view certain streaming sites here in Germany, and it works fine.
However, when I use Safari, it's not using the custom DNS. (There is a test page to confirm that it is working.) It is using my ISP's default DNS, which I gather it is getting via the gateway 192.168.1.1.
If I remove 192.168.1.1 from my DNS list, Safari cannot resolve ANY name -- apple.com, google.com, etc. Nothing at all.
Why is that? Why won't Safari simply use the custom DNS, as Chrome does?
I have tried flushing the DNS cache, deleted all Safari temp data, flushed the Safari cache -- but no change.
Safari will only resolve sites if I re-add 192.168.1.1 to my DNS list.
Very frustrated -- any ideas?
MacBook Pro, OS X Yosemite (10.10.5)
Posted on Sep 8, 2015 2:40 AM