Enough said.

Incorrect in some aspects. All caching means is IF a recursive DNS server had done a lookup on your domain recently enough that the TTL hadn't expired, then you use the recursive DNS server's cached copy of the DNS record.

If the recursive DNS server doesn't have a cached copy of the record, it will simply go through the resolution path to get to the authoritative DNS provider and get a fresh copy of the DNS record.

Having a low TTL just means that more queries will hit the authoritative DNS provider since the recursive DNS provider is less likely to have a cached copy of it. It's not bad necessarily to have a low TTL, it just means more queries are generated which results in a little bit longer DNS resolution time compared to using a cached copy. In the case of Dynamic DNS, you are never really going to care/notice any speed hit caused by less caching.

This # doesn't include any domains transferred away from GoDaddy that were delegated to non-GoDaddy nameservers. The 21,000 number is only for domains that used GoDaddy's nameservers for DNS. So the actual # was higher than 21,000.

The question is what is the real number of transferred away domains? I don't know if any of those statistics are available publicly.

Yeah that DNSSEC page looks very old, I hadn't even realized it existed until now. Thanks for bringing this up. We are working on rewriting docs so I will make sure this gets addressed.

Once you have a registered domain in your account, for supported TLDs there is a 'DNSSEC DS records' section on your domain registration page.

We added DNSSEC support for the major TLDs several months ago, sounds like right after you looked. The domain registration page for supported domains will show a section for adding DS records.

Yep, we support DNSSEC on .com, .net, .org, .biz, and .se. No need to use us for DNS (although you certainly can, any DynECT Managed DNS products support DNSSEC).

The Google Authenticator app for the iPhone works perfectly.

Works if you live not in the same market as your favorite team. If you want to watch in market games, then you can't, they are blacked out on all streaming sites.

If they can get blackouts to end for local games, I'm done with cable.

There is an implied trust when downloading an app from the official app store that that the app is safe for use. Users are far more likely to download something from the official app store compared to going to some random web site and allowing it to install stuff on your phone.

Comparing that to going to a web site that can jailbreak you phone is not the same situation.

Say what you will about the App Store review policies, but at least I know someone at Apple has personally looked at every app and its update I installed on my phone so a situation like this won't happen.

That would slow down DNS queries significantly having to run multiple checks against nameservers. That would be a great way to slow down the Internet.

1) Get a static IP address for your mail server if you don't already have one. Many mail servers use DNSBL blacklists that distrust anyone with a Dynamic IP address.
2) Get your ISP to configure Reverse DNS for your mail server's IP address. Many mail servers reject mail because Reverse DNS isn't configured properly.
3) Make sure your server is set to not run as an open relay.
4) Have a proper abuse@ and postmaster@ e-mail addresses so e-mail providers who claim to have spam complaints against your domain can actually send them to you.
5) Setup an SPF record (openspf.org has a great wizard for this) for your domain. SPF records basically specify which mail servers are allowed to send mail from your domain. This will help cut down on spammers spoofing e-mail addresses at your domain and increases the odds of legit e-mail not being marked as spam.

Not all of these will guarentee delivery of any e-mail, but they can certainly improve the odds.

Only thing I remember (I was just 3 at the time) was seeing my mom pick me up from preschool and clearly look like she had been crying. She had apparently been sitting in the car for an hour listening to the coverage of the launch and the aftermath. She didn't tell me what happened, but explained that people were going up to the stars and something went wrong. We lived (in fact still do) in New Hampshire, so this hit especially close to home for everyone around here.

A few years later (in fact, when we went to the opening of the planetarium in Concord, NH named after McCauliffe) my mom told me about that day and I finally was able to link up the memory of her crying to the actual event.