Wikipedia defines Adware as “Adware or advertising-supported software is any software package which automatically plays, displays, or downloads advertising material to a computer after the software is installed on it or while the application is being used.”
This guy makes some good points, the OpenDNS as Adware idea not being one of them though. He’s had some issues with the typo fix feature of OpenDNS and the OpenDNS search page coming up when it shouldn’t.
So what happens when it doesn’t know the IP address you ask? Well sometimes it returns no answers
[email protected] ~ $ dig verizonn.com @184.108.40.206
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
And sometimes it gives you back their server. (asdverizon.com. 1 IN A 220.127.116.11) any request to 18.104.22.168 results in a search the attempted url being ran through their systems. If im not misunderstood, they make their money off of adds displayed at this time… therefore, the more they don’t catch, the more money they make on advertising? Ok so I guess for their software it “Pays to be stupid”
Simply because an application doesn’t provided the expected results doesn’t mean it’s adware. OpenDNS seems like the kind of company who is out to stop adware and other sorts of internet baddies. That post is worth a read, it does a nice job of bringing to light some problems in OpenDNS. And, I don’t think the guy was actively trying to take the “OpenDNS is Adware” stand, he did file that post under “Talking Shit” after all. heh.
Another interesting OpenDNS related post comes from Thomas Ptacek. Thomas has noticed OpenDNS actually takes longer to resolve some domains than, say, your ISP’s DNS servers.
74ms longer via OpenDNS. How much of that is network latency? You could turn off recursion, but OpenDNS doesn’t support it, so instead query for OpenDNS’s own names:
nsping -z opendns.com 22.214.171.124
+ [ 22 ] 55 bytes from 126.96.36.199: 261.771 ms [ 192.468 san-avg ]
41ms. Weak evidence that it takes OpenDNS 33ms longer to look up random names at Google on my DSL connection? Note also that all the OpenDNS queries “succeed”, because OpenDNS sends you to a landing page for typos.
Some pretty interesting comments going on at that post too. David Ulevitch and Thomas might end up getting together to do some testing on DNS caches and overall performance. David made a comment in my previous post on OpenDNS in which he explains some of the new features they’re working on:
I agree 100% about us needing to be more transparent. The three biggest things we are working on right now are:
1) Getting account preferences up and running so people can just enable and disable the various features they are working on.
2) Providing a much clearer understanding of where our phishing data comes from and what happens if we make a mistake
3) Bringing up our London datacenter and adding in a bunch of peering and other network connectivity to our existing sites.
I’ve really only witnessed one problem with OpenDNS. This is a prime example, try navigating to http://www.tehserver.us/. It takes you to the OpenDNS search page, right? Well, the first link displayed on the search page is really where I want to go. So, I click the first link and I’m taken right back to the OpenDNS search page I was just on. So, there’s apparently no way for me to get to www.tehserver.us using OpenDNS. Granted, tehserver.us isn’t totally legitimate, it’s definitely not breaking any sort of laws. Perhaps the spellcheck is getting confused. The domain is tehserver.us, not theserver.us.
I’ve been using OpenDNS for about 5 days now. I am going to do some testing tonight at home to see if OpenDNS actually serves up info quicker than my ISP’s DNS servers. I will post the results and how I went about testing. That is, provided I have power at home, there’s been some awesome storms rolling through the last couple days. A welcome event for the farmers around here though.
UPDATE: I can get to tehserver.us with no problem now, I never even see the OpenDNS search page. David mentioned he’s opened a bug in bugzilla for the developers to check out. He also mentioned this post on OpenDNS by Greg Keene. Greg takes a look at OpenDNS and fears even one security breach could make OpenDNS disappear:
My concerns? The obvious, security and security. Will temptation to generate advertising overcome their ‘do good’ nature? We’ll have to see. A huge, obvious hole is their own security. If they get hacked, then their users are effectively exposed — don’t underestimate this. I’d like to get more people using them so we can really find how good they are. My thought is that one security breach could kill these guys, even an exposed exploit would be a very bad thing.
Give it a try and let me know what you think.