Comments on: OpenDNS out loud: two audio clips http://blog.opendns.com/2006/07/31/opendns-out-loud-two-audio-clips/ Making the Internet safer and faster Tue, 07 Feb 2012 20:12:30 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: David Redekop http://blog.opendns.com/2006/07/31/opendns-out-loud-two-audio-clips/#comment-160 David Redekop Wed, 02 Aug 2006 01:25:31 +0000 http://blog.opendns.com/2006/07/31/opendns-out-loud-two-audio-clips/#comment-160 Thanks for clearing up the issue, John, I'll make sure I communicate it properly next time. We will also be talking about OpenDNS at our next A-Channel Morning London show. I'll be happy to send you a clip of that as well. Thanks for clearing up the issue, John, I’ll make sure I communicate it properly next time. We will also be talking about OpenDNS at our next A-Channel Morning London show. I’ll be happy to send you a clip of that as well.

]]> By: John Roberts http://blog.opendns.com/2006/07/31/opendns-out-loud-two-audio-clips/#comment-158 John Roberts Tue, 01 Aug 2006 20:03:14 +0000 http://blog.opendns.com/2006/07/31/opendns-out-loud-two-audio-clips/#comment-158 Yes, we should have said so. Been considering your note. The second part was fixed yesterday. The first part... requires more thought, and may have some unintended consequences. When people move nameservers for their domain and haven't reduced their TTL (time to live) to a low number, then their domain might not resolve temporarily, leading to our search results page. Obviously, that's not a permanent situation. Anyway, that's one example where your first solution requires more tinkering. But we appreciate your comment and your choice of OpenDNS. Yes, we should have said so. Been considering your note. The second part was fixed yesterday. The first part… requires more thought, and may have some unintended consequences. When people move nameservers for their domain and haven’t reduced their TTL (time to live) to a low number, then their domain might not resolve temporarily, leading to our search results page. Obviously, that’s not a permanent situation. Anyway, that’s one example where your first solution requires more tinkering.

But we appreciate your comment and your choice of OpenDNS.

]]> By: Gabriel Bauman http://blog.opendns.com/2006/07/31/opendns-out-loud-two-audio-clips/#comment-157 Gabriel Bauman Tue, 01 Aug 2006 19:26:27 +0000 http://blog.opendns.com/2006/07/31/opendns-out-loud-two-audio-clips/#comment-157 Wow, you already fixed the search results issue! Cool. Wow, you already fixed the search results issue! Cool.

]]> By: Gabriel Bauman http://blog.opendns.com/2006/07/31/opendns-out-loud-two-audio-clips/#comment-154 Gabriel Bauman Mon, 31 Jul 2006 22:20:31 +0000 http://blog.opendns.com/2006/07/31/opendns-out-loud-two-audio-clips/#comment-154 Hi guys, Just noticed that because OpenDNS resolves 'typos' and other misspelled domains as if they exist, my browser's URL history is full of 'typo' URLs. It's annoying! In thinking about possible solutions, I came up with this. Why not resolve typoed domains to a web server that does an HTTP 301 Moved Permanently redirect to either your search results or the corrected URL? Browsers are not supposed to keep URLs that lead to 301s in their history according to the RFC, so theoretically my history wouldn't be full of cruft if you did this. I would much rather redirect to search.opendns.com than find search results at a non-existent domain. Another plus for you - my search queries would be accessible from my history even when I'm not using your DNS servers :) Also, when bringing up search results, please don't search for the 'typo-corrected' term. For instance, hit http://kwalms/ ... You'll find that the term actually searched for is 'alms'. Much better to say "Did you mean to search for... alms?" at the top of the actual search I requested. Anyway, thanks for the service. Hi guys,

Just noticed that because OpenDNS resolves ‘typos’ and other misspelled domains as if they exist, my browser’s URL history is full of ‘typo’ URLs. It’s annoying!

In thinking about possible solutions, I came up with this. Why not resolve typoed domains to a web server that does an HTTP 301 Moved Permanently redirect to either your search results or the corrected URL? Browsers are not supposed to keep URLs that lead to 301s in their history according to the RFC, so theoretically my history wouldn’t be full of cruft if you did this. I would much rather redirect to search.opendns.com than find search results at a non-existent domain. Another plus for you – my search queries would be accessible from my history even when I’m not using your DNS servers :)

Also, when bringing up search results, please don’t search for the ‘typo-corrected’ term. For instance, hit http://kwalms/ … You’ll find that the term actually searched for is ‘alms’. Much better to say “Did you mean to search for… alms?” at the top of the actual search I requested.

Anyway, thanks for the service.

]]>