[Axlin]

Today started off just like usual. Everything was running great, and I was using Safari to browse the web just like anybody else would. No issues at all. But then, for no apparent reason that I can possibly think of, Safari decided to give me troubles. I can launch Safari just fine, and I can type in a URL and go to it just as normal. However, once the page loads, Safari simply refuses to load any pages that I type in or any links that I click on. It will just sit there and do nothing. This has me completely stumped… I have never experienced an issue like this before. I've even tried a repair disk/permissions with no luck, and I've reinstalled Safari completely off my OS X disc with no luck. Camino and Firefox work just fine, as well as every other application that uses an Internet connection, so it certainly isn't an issue with my connection. Has anybody heard of an issue like this? I simply do not know what to do, and I really do not want to have to switch to Firefox over this.

I do have some plug-ins (SafariStand, AcidSearch, PithHelmet, and ForgetMeNot), but I just removed them and the problem still persists, so I don't think that's the issue either.

Thanks.

EDIT: I… I don't understand it. I got it to work by following the advice in this thread - Going into my System Preferences > Network panel, selecting my connection and clicking the "Configure" button, going to the TCP/IP tab, and entering "4.2.2.2" in the "DNS Servers" box. After doing that (and rebooting my computer), Safari is working just fine again. Now that Safari is running properly, I'm pretty curious as to why it works now. According to people in that thread, 4.2.2.2 is one of Verizon's domain server numbers. But why would that work for me if I'm on a university connection that has no affiliation with Verizon whatsoever?

[Old Toad]

Have you tried: 1 - emptying Safari's caches, Command+Option+E, and 2 - deleting Safari's preference file, com.apple.Safari.plist?

Also if you haven't rebooted recently you might try that. Doing so has been know to cure a number of issues.

[Axlin]

I've actually gotten Safari to work again by the aforementioned "edit" section, although I have changed the "4.2.2.2" to OpenDNS's numbers and have noticed much better performance than ever before. Thank you for your response, Old Toad.