There are still games being played with it. A year ago I was at a talk where a fairly cute attack was outlined. One element of it was that folks were publishing BGP routes to ip4 addresses that are (as of now) dark. I can't remember now the exact value of advertising routes to IPs that don't exist, but there was value to doing it, and no indication that the BGP gatekeepers were paying close attention to it. No traffic for legitimately assigned addresses was interrupted; who was complaining? Which NOC employee at a tier 1 or tier 2 carrier has time to analyze phishing email misdirects?
As far as folks who want to trust SSL and plan to not use a system if the SSL cert isn't correct because DNS has been compromised upstream: all well and good for you. If you give the pointy haired boss who runs personnel a browser popup with two buttons, one of which says "you can't work for a few hours while IT figures out what's wrong with this crypto" and one of which says "you can keep doing what you think is your regular work by pressing this button," which button will get pushed?
And if the choice comes up a second time, because the first time the PHB accidentally made the safer decision the first time out?
Unless you're using a proxy that's set up to reject certs that don't pass, with no bypass mechanism, there will be a lot of people breaking SSL intentionally from inside the firewall; they won't understand what they're doing, but they'll compromise their own systems again and again.
How confident are you that the people whose computers handle your transactions are protected from making this mistake? Not just banking, but medical, pharmacy, car insurance, concert tickets....