Why does Amazon no longer work in Safari?

Yes, Linc likes to give the impression that he is the only contributor here who knows anything about anything.

Obviously, all the publications quoted here are lying through their teeth:

http://www.opendns.com/home-solutions

Linc:

This was discussed in the Lounge. You were out-voted.

I gave them to you in my post, which you said worked!

If you've informed yourself about the privacy implications of using OpenDNS, without trusting the opinions of ignorant strangers or the company's marketing material, and you're satisifed, and OpenDNS is working for you, then you don't need to do anything else. I am not telling you not to use OpenDNS. I'm telling you not to use it in an uniformed way. I would never use it, but my opinion doesn't matter. Neither does anyone else's, except yours.

We haven't yet established what DNS service you're using now. Your primary DNS server is your router, and the secondary one is Frontier Communications, which I assume is your ISP. If you want to pursue the matter further, please open your router's administration page (if it's not an Apple device) or AirPort Utility (if it is an Apple device.) Find the addresses of the DNS servers the router is using and post them here. Again, this is only necessary if you have misgivings about being tracked by OpenDNS, as you will be from now on.

I've got to agree with Klaus. From what you describe, and from the fact that you tried the OpenDNS addresses and that got Amazon working, I would guess that your ISP's domain name servers have been "poisoned." DNS poisoning happens when a hacker manages to get a bogus entry into a domain name server, so that, for example, the address "www.amazon.com" resolves to some IP address other than the correct one.

This is generally done for phishing purposes, so that the IP address leads to an Amazon look-alike page. When you try to log in, the hackers get your Amazon login information and go hog-wild on your account. In fact, the fact that you tried to log in and couldn't strongly indicates phishing... after all, a login on a phishing site must, by definition, fail, since it's not the real site. I would strongly advise that you change your Amazon password ASAP and check your account (and associated credit card) for bogus charges.

As for Linc's concern about OpenDNS tracking you... well, that's a darn sight better than a poisoned domain name server giving you malicious IP addresses! Besides, most sites you visit online are going to try to track you one way or another. There's really no way to avoid it, other than to only use public computers at a variety of different locations... or not use a computer at all.

I should add that the DNS servers are certainly not "poisoned," and it's a common response whenever net privacy issues are raised for people to say something to the effect of "You have no privacy anyway -- get over it," or "You only need privacy if you have something to hide."

I should add that the DNS servers are certainly not "poisoned,"

Then how do you explain the symptoms of the problem? How do you explain that the problems went away when skippermi changed DNS servers?

The problem is caused by faulty DNS, as the OP already knows. That doesn't mean the faulting server has been the target of a poisoning attack.

The problem is caused by faulty DNS, as the OP already knows. That doesn't mean the faulting server has been the target of a poisoning attack.

It also doesn't mean that it hasn't. Having trouble with just Amazon is very suspicious, especially given the failed login attempts on the rare occasions that Amazon actually seems to load. A faulty DNS server would be unlikely to fail for just that one site and no others.

Only power users should be messing around with their DNS servers and for a particular reason.

It should not be used to fix issues with computers or even ISP DNS issues as they will likely have their issues fixed in short order.

Using a alternate DNS for the short term is acceptable provided the ISP DNS is the source of the problem, however there are more drawbacks for most.

It is wrong to recommend a alternate DNS without considering the original problem posters physical location. Because the alternate DNS requires a server in the general location of the ISP's server delivering the content or else Akamai based downloads from the ISP come from a server farther away. Apple uses Akamai ISP based servers for content all the time.

Read why using Google DNS / OpenDNS is a bad idea

http://apcmag.com/why-using-google-dns-opendns-is-a-bad-idea.htm

Usually the ISP's DNS will resolve their issue in a short time, it makes little sense to recommending a alternate DNS and have the OP suffer with permanent problems over something that will get resolved on the ISP end shortly if they would just leave complicated things alone.

Recommending only one alternate DNS is also wrong, there is Google DNS and others as well, with Google DNS actually having more servers in more locations than OpenDNS.

It is wrong not briefing the OP on the privacy policies of alternate DNS servers, what they collect and why about web users traffic. OpenDNS is a for profit company, so is Google, they are likely selling a users web traffic data to generate more income or provide to advertisers like Google does.

It is wrong to recommend a alternate DNS based on performance without them running a test to see which DNS service is actually the fastest. Another or even the ISP's DNS might be the best fit and fasest.

Also, I have run this test often and it's NOT always the same result. Sometimes another is faster, sometimes Google, sometimes it's ISP's. So there is no guarranty running the test once and swtiching the DNS is always going to be the fastest.

Google provides such tool here called namebench.

https://code.google.com/p/namebench/

DNS servers resolves only the domain name into a IP address, it's the ISP servers that download the web pages and make contact.

Thus services like OpenDNS, for money or advertising, can block some sites /content catagories from resolving on one's entire local area network. It's another level of complexity that most users cannot handle.

If OpenDNS want's to promote their service, let them take out advertising and let professionals set common users machines up with it.

Disclaimer: I actually have used OpenDNS and other alternate DNS services, thus I speak from experience.

Those are your ISP's DNS servers. Usually it's best not to change them, but in your case, they're not always returning correct results. You could try communicating with the ISP about the problem, but that would probably be a waste of time. Your other options are to stick with what you now have, to use another public DNS service, or (if you're an advanced user) to set up your own DNS that doesn't depend on any other recursive resolver.

If you choose to use public DNS, the other ones that I've tested are Google DNS (which has privacy implications even worse than those of OpenDNS), and Level3. A more complete list is here:

Free & Public DNS Server List (Updated February 2013)

You mentioned in your first post that your tablet was working OK. What brand of tablet and how is it connecting to the Internet?

Not sure why it would work with the Nook and not the Mac. Totally unaware of how the Nook does networking.

Have you ever told us what brand of router you are using?

So where are you at now? Are you using rhe Open DNS DNS service or are you using your ISP's DNS service and are you get to Amazon or not right now?

Try this open Network Utility (use Spotlight enter Network Utility) Across the top are tabs select the Lookup tab. In the box enter www.amazon.com, press Lookup. Cut and paste the out put of the window here.