I used to be an OpenDNS user, but after I discovered that their DNS name-servers may be slower, I stopped to use them. Now I use Google Public DNS. My ISP's ones are a bit faster, but sometimes they go offline (they have bad up-time). I find Google Public DNS to be more resilient, so I chose them. Share your options and opinions.
It's not about speed, you think it matters if one is 5ms faster? Firstly, it's about trust. Like I could trust Google, or even Comodo? (lol!) for that matter, with anything. Secondly, database size. No one has the sheer dictionary of websites that OpenDNS has, also, OpenDNS has Phishtank behind it, which makes it even more powerful. If you want to know a little trick I use, don't set your OpenDNS IP's the way OpenDNS tells you, everyone does that, so most of the strain goes on the primary server. Set the secondary server as primary and the primary as secondary, then enjoy the -10ms. You can usually discover which is better by pinging both with about 30 packets and deciding for yourself. As I'm sure you've guessed, I selected OpenDNS.
OpenDNS. For some people, it's faster than their ISPs (like me with my current horrible cable ISP). For other people, it's a hair slower than their ISPs (like when I had Comcast). However...I have all my SMB clients setup using OpenDNS for DNS forwarding...because what's good about OpenDNS..is they filter out known malware sites. So you get an added layer of protection for your network. And that's worth a lot.
I don't usually use one, but I've switched to Google DNS for the next month or so since I'm back at my parents' for summer, and the local ISP is absolutely awful. I use a ton of other Google services, so it just seemed like a no-brainer. No registration required to use was definitely a plus.
You may want to test your DNS server speed using the two tools below to see if there is a difference: Namebench DNS Bench
Thanks for posting, InfinityAz. A mixed bag of results I got using GRC's tool. I use OpenDNS, BT is my ISP. I'm in the UK. 208. 67.222.222 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ + Cached Name | 0.039 | 0.050 | 0.058 | 0.004 | 100.0 | + Uncached Name | 0.047 | 0.203 | 1.106 | 0.255 | 100.0 | + DotCom Lookup | 0.050 | 0.124 | 0.323 | 0.060 | 100.0 | ----------------+-------+-------+-------+-------+-------+ resolver1.opendns.com OpenDNS, LLC 208. 67.220.220 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ + Cached Name | 0.039 | 0.051 | 0.062 | 0.005 | 98.0 | + Uncached Name | 0.044 | 0.186 | 1.074 | 0.228 | 100.0 | + DotCom Lookup | 0.046 | 0.126 | 0.202 | 0.052 | 100.0 | ----------------+-------+-------+-------+-------+-------+ resolver2.opendns.com OpenDNS, LLC ****** ______________ | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.037 | 0.051 | 0.058 | 0.004 | 100.0 | - Uncached Name | 0.041 | 0.122 | 0.383 | 0.092 | 98.0 | - DotCom Lookup | 0.041 | 0.052 | 0.058 | 0.004 | 100.0 | indnsc70.ukcore.bt.net BT MDIP Dynamic Address Pools and infrastructure ****** 8. 8. 4. 4 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.049 | 0.059 | 0.066 | 0.003 | 100.0 | - Uncached Name | 0.066 | 0.197 | 0.383 | 0.092 | 100.0 | - DotCom Lookup | 0.073 | 0.159 | 0.319 | 0.063 | 100.0 | ----------------+-------+-------+-------+-------+-------+ google-public-dns-b.google.com Level 3 Communications 8. 8. 8. 8 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.050 | 0.060 | 0.068 | 0.004 | 100.0 | - Uncached Name | 0.065 | 0.184 | 0.385 | 0.095 | 98.0 | - DotCom Lookup | 0.078 | 0.161 | 0.264 | 0.055 | 100.0 | ----------------+-------+-------+-------+-------+-------+ google-public-dns-a.google.com Level 3 Communications ****** In Conclusion Usage Order Nameserver IP Speed Rank (OpenDNS) ----------- --------------- ---------- 1 208. 67.222.222 1 2 208. 67.220.220 2 unreliable "One or more system nameservers is NOT 100% reliable! DNS reliability is extremely important, since lookup requests that are dropped and ignored by nameservers cause significant delays in Internet access while the querying system waits for a reply. The system is then finally forced to reissue the query to the same or to backup nameservers. While your system is patiently waiting for a reply, you are impatiently waiting to get on with your Internet access. During this benchmark test, the nameservers being tested did not reply to some of the DNS queries they were sent." ^^ GRC's only red warning with OpenDNS' service for me. It recommends ... Recommended Actions: Before you make any changes, you should probably run the benchmark a few more times at differing times of day to make sure that the troubling reliability is an ongoing problem and not just a brief occurrence. You may also wish to consult the "Tabular Data" page which summarizes all benchmark results in numeric tables. The numbers make it easier to see exactly how unreliable your system's nameservers are compared with the available alternatives. (And also how the alternatives' performance compares.) Well that was a good waste of 30 mins when you are snowed in.
1. Looks like google takes quite a bit longer than OpenDNS. 2. Looks like I was right that swapping OpensDNS primary/secondary IP's is a good idea
I don't trust number 1. . I used DNS Bench I don't have it perfect yet the utility complains that I used one address belonging to level three because they say they are unreliable. I have some more fine tuning to do but getting better.
ive used namebench personally and its perfectly fine, but if ur worried u can run it sandboxed and it still functions fully.
OpenDNS, I like that it blocks mallware, even ADs or possible silent downloading from similar webpages.
DNS Advantage. I have tried Open DNS and Google DNS, the later worked fine but blocked out Facebook for quite a few days so DNS Advantage gives me the best performance. I also use it combined with PDNSD which is a permanent caching DNS server in Linux.
