Test with iPhones. No pre-loaded carrier bloatware, same exact OS across all carriers.
Personally traveling to and through Boston is a 100x better than it used to be because of the Big Dig. Not to mention it reconnected two parts of the city that the original above ground highway effectively severed from each other, allowing for an insane amount of development in the seaport area since (http://www.bostonmagazine.com/2012/07/rise-seaport-district-boston/). The entire area has been transformed.
If there is evidence of Google doing evil, then it's easy to create an eBay listing.
Assuming you mean traditional round-robin A records, the timeout(s) you still have to suffer through would kill your latency.
If your talking about DNS providers (disclaimer, I work for Dyn) with advanced features that detect a failover event occurring and will only serve healthy A records, then that is a different story.
They will probably use something like Google Authenticator: http://en.wikipedia.org/wiki/Google_Authenticator
Last time I knew (granted, couple years old knowledge), the Windows version of Java didn't install updates automatically. Has that changed?
Seems like every time I use a Windows computer, there is the Java update icon in the system tray.
My backup setup is pretty simple. An Apple Time Capsule for hourly local backups that I can access right away, and Backblaze for off-site backups in the event of theft, fire, etc. I never have to worry about backups anymore.
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
The Google Authenticator app for the iPhone works perfectly.