The following release is not being distributed far and wide.

OpenDNS Thanks Its Users with Cranberry Choice for Thanksgiving

Canned or whole cranberries, intelligent DNS platform offers users choice about how they want their turk…err, DNS.

PLYMOUTH ROCK, Mass. – Nov. 22, 2006 – Just in time for the American holiday of Thanksgiving, OpenDNS offers additional choice in DNS: canned cranberry sauce or whole cranberry sauce or none at all.

All OpenDNS users enjoy a fast, free, reliable DNS service, with the safety of phishing prevention and the intelligence of typo correction. That service is available with or without an Account. With a free OpenDNS Account. users can choose their own DNS preferences. Those preferences now include cranberries: canned, whole, or none at all.

By default, OpenDNS will deliver DNS without cranberries. But with an account, OpenDNS users can change their cranberry preference and have that taste distributed around the global OpenDNS network instantly.

Canned versus Whole

It’s a debate that stretches back generations: which kind of cranberry sauce goes best with the traditional turkey dinner? The advocates of canned sauce praise the consistency, in texture, mouth feel, and shape, and welcome the common thread that weaves together Americans throughout the nation. The ridges left by the sturdy can mean Thanksgiving to many.

For others, nothing says Thanksgiving more than whole cranberries, in all their aromatic tartness, waiting to be dribbled over their turkey (and anything else!). The variations are cherished, and the “natural” state gently evokes the first Thanksgiving’s hardships (without actually requiring suffering).

Further background may be enjoyed at “The Great Cranberry Sauce Debate.”

Note: For those who stay on the side of this great divide, stay with the default: DNS without cranberries. It’s still free, fast, and reliable.

Next year’s preference? Indicate whether you like your DNS with dark meat, white meat or drumsticks.

P.S. Happy Thanksgiving. OpenDNS understands that the cranberry preference may be of limited value to those who do not celebrate Thanksgiving; we promise to consider other preferences appropriate to local holidays.

See the new tab up there, at the far right? It says My Account. Go ahead and take a look. Or read on for why you’ll want to create a free account. You can find the tab and Sign In link at the upper right of every page of the OpenDNS website.

OpenDNS invited the public to use its free, reliable DNS service for the first time on July 10, 2006. Less than a week later, we introduced preferences for OpenDNS, which gave the individual user the opportunity to manage their DNS in a way that had never before been possible. Later, at customer request, we used our platform to offer choice in their response to Cameroon’s TLD policies.

OpenDNS Accounts represents the next step in our commitment to give our customers choice and control.

We talk a lot about “Safer, Faster and Smarter” DNS built on a rock-solid and reliable foundation. A big part of being safer and smarter means giving you control. That’s what OpenDNS Accounts is all about.

When was the last time your DNS improved?

It doesn’t matter if you have one IP at home that you manage or a massive network of disconnected offices — OpenDNS Accounts is for you.

Secure
Registration, sign in, and all profile and preferences are managed with a username and password on a secure, encrypted site using SSL (like your bank does).

Dynamic DNS Support
OpenDNS Accounts support the use of dynamic DNS (DDNS) update mechanisms to allow you to securely manage your Account and get your preferences even with a dynamic IP address. Read for details. Note: Because OpenDNS uses SSL, there are several very good DDNS clients which do not (yet) work. We are going to encourage various developers to add support for SSL to their otherwise very strong DDNS software.

Statistics
Everyone from individuals to network operators will enjoy a bit of insight into statistics about their DNS usage. How many DNS requests per day do you make? How many individual domains per day do you resolve? On that pretty graph I see for the OpenDNS service, what am I contributing? Basically, we’re taking the stats we show the public and giving you similar insight with the stats that relate to your DNS traffic.

Just as a heads up — while DNS resolution is blinding fast (as always), our stats processing happens (as our network guys say) out-of-band and is done separately. You will not see statistics immediately (at least, not just yet). It may take as long as 48 hours for your stats to appear.

We feel strongly that this is a platform for DNS unlike anything that has ever existed before and continues to help OpenDNS bring about evolutionary changes to the DNS that dramatically change the end-user experience.

P.S. If you have OpenDNS preferences, they will continue to work until they are superseded by an OpenDNS Account with the same IP address. We suggest that anyone using OpenDNS preferences set up a free account now and verify your IP address.

We’ve been quiet recently. Too quiet.

Seriously, all of us are focused on two large projects, each of which will see the light of day shortly. Both of these efforts won’t surprise those who have been paying close attention to some of our previous writings.

Just to add to the behind-the-scenes fun, our growth (thank you!) has accelerated some of our storage upgrade plans, since we hate falling behind in our stats processing. As noted on the system status posts [1, 2], DNS services are not affected by stats processing, deliberately — but it means our pretty graphs get stuck until we catch up.

(And, yes, London is still in progress.)

I’m doing this blog post in two pieces; a short explanation up top and then a more technical explanation down below. Pick one or read both and learn a bit.

Just the facts

If you want to use OpenDNS nameservers and DNSBLs (DNS real-time Blacklists) on the same server, computer or network, go right ahead. We’ve rolled out a new feature today that allows you to use our much-loved typo-correction service without worrying about blocking email if you’re running a mail server, too. We went ahead and rolled this out as as a system upgrade so there’s no new preference for it. We’ve updated the FAQ entry on mail servers accordingly. Now DNSBL spam prevention and typo-correction go together like peanut butter and jelly (or chocolate… your choice).

If you were previously not using the typo-correction service because you also ran a mail server then head on over to the preferences page and re-enable it.

Talk nerdy to me

DNSBLs carry information about known IP addresses in their zone of DNS. This is often used to combat spam because a mail server can ask a DNSBL “Do you know anything about this IP?” They cleverly use the DNS to make this process quick and seamless. A mail server that gets a request to deliver mail from 192.168.1.2 asks a DNSBL: “Do you know anything about 2.1.168.192.in.yourdnsbl.tld?” and the DNSBL either says “yes I do” or “no I don’t.” The problem is created because when a mail server is using OpenDNS and asks us to correct typos, we interpret the “no I don’t” answer (called RCODE=3 or NXDOMAIN) as a typo that should be forwarded off to our typo-correction service. This causes a mail server to not see the “no I don’t” and instead believe that the answer was “yes I do” which can cause a mail server to block a message thinking it’s from a spam sender. Previously, the only way to fix this was to disable typo correction, one of the benefits of using OpenDNS.

Our solution has been to disable typo-correction for DNSBL-matching requests. What’s a DNSBL-matching request? Any request greater than six labels which has four numerical octets within the IPv4 addressing space for the last-most labels is considered a DNSBL-style request. This wasn’t offered as a preference as turning this off would only lead to confusion, especially with typo-correction enabled.

End of the story? You can get the typo-correction you want and run a mail-server that uses DNSBLs without worrying. Enjoy!