Josh — I agree about that during development you often have to force a flush. However it’s good that you can actually force a reload in this setup, whereas you can’t if you just use your ISP’s recursive DNS :)
John — At the end I want to check whether a domain exists or not. In shell I just try to resolve its A or NS records, and I prefer to see NXDOMAIN than OpenDNS’s records coming back. There are also many different domain name based RBL, where I just can’t assume that OpenDNS has a exception for them.
Also typo correction gives you an indeterministic result when you perform test on inputs, if input is a hostname/domain name. Not good if you are building an application that relies on it.
At the end I see typo correction only useful for web browsing, as the correction is done by forwarding the HTTP traffic to your web server. I understand that it provides OpenDNS’s revenue stream, and I’ll use it on my desktop, but no so with servers that I am hosting applications.
Josh — I agree about that during development you often have to force a flush. However it’s good that you can actually force a reload in this setup, whereas you can’t if you just use your ISP’s recursive DNS :)
John — At the end I want to check whether a domain exists or not. In shell I just try to resolve its A or NS records, and I prefer to see NXDOMAIN than OpenDNS’s records coming back. There are also many different domain name based RBL, where I just can’t assume that OpenDNS has a exception for them.
Also typo correction gives you an indeterministic result when you perform test on inputs, if input is a hostname/domain name. Not good if you are building an application that relies on it.
At the end I see typo correction only useful for web browsing, as the correction is done by forwarding the HTTP traffic to your web server. I understand that it provides OpenDNS’s revenue stream, and I’ll use it on my desktop, but no so with servers that I am hosting applications.