“A study conducted by IDC determined that only 41% of small companies and 35% of large organizations monitor Internet DNS response times.”
“DNS failures account for as much as 29% of system downtime costing companies millions of dollars.”
The Domain Name System (DNS) is arguably the single most important part of the internet. Just think: If websites only had a numerical lookup… our Rolodex’s would be massively confusing. Why don’t webmasters/hosts treat DNS with the same priority? DNS servers carry such a high importance. Without them, no internet. They are often the target of massive Distributed Denial of Service (DDOS) attacks. Are your DNS records configured properly and secure?
DNS Performance & Security Enhancements
Most of the Internet is run on Berkeley Internet Name Domain (BIND) based servers. There have been a lot of failed attempts to create a BIND alternative (GnuDIP, MooDNS, Dents, OakDNS, CustomDNS and dproxy). A couple of active projects are PowerDNS, NSD, djdns and MaraDNS. All boast better security and performance improvements in different environments. If you are hosting your own DNS, you owe it to yourself/network to review your options.
Minimizing down-time with TTL
Most of us have been effected by DNS outages. There is not much you can do when a record gets out of whack or a server goes down. You can flush your local cache, maybe even try to resolve against a different server, but the only real cure is time. That is because each DNS record has a setting called Time to Live (TTL). This is how long the record should persist. Once this time expires, a new record is fetched. Also, if the servers aren’t available, you don’t get a record.
A good rule of thumb when setting your TTL is to use your average visitor time. For example, if the average visitor spends five minutes on your site (check your analytics), you should set your TTL to 300 (in seconds). The idea is; in the event of a failover, it has the least impact on visitors and doesn’t require a performance hit for numerous DNS lookups. Some DNS providers won’t allow a TTL setting this low. A lower TTL mean more DNS queries and ultimately more expense.
Should I outsource my DNS?
A lot of network architects will actually advise webmasters to host their own DNS records. The route/latency will be the same as HTTP traffic, thus making lookup time approximately the same as a web requests. It also reduces the risk of outages caused solely by DNS. If they are hosted on the same subnet, routing glitches are minimized. If they are on the same server as your website, it will even further reduce the risk of DNS only outages.
However, if you don’t have the time/experience to monitor, review logs and maintain your DNS servers, outsourcing is a great option. But beware, all DNS networks/servers are not created equally. If you are hosting your records with a budget registrar, chances are you are at risk. They are often the target of DDOS attacks, endure lengthy outages/maintenance and have congested networks. Security by obscurity; in the last two years I have had clients with DNS outages lasting greater than 6 hours at two of the major registrars.
The Cadillac of DNS currently is NeuStar’s UltraDNS. They have a globally redundant/optimized network with proprietary DNS software powered by Oracle replication. However, they charge by the query, so if you have a busy site, it will get expensive in a hurry. Another high-end service is Netriplex. For small to mid size company’s the only way to afford either of these services is to increase unfortunately to your TTL.DNS Made Easy. They have a great feature-set, excellent and knowledgeable staff all at a great price.
Search Engine Optimization (SEO)
There have been reports of falling Search Engine Results Placements (SERPs) taking drastic drops soon after a DNS change. Changing just the IP address has not caused any notable problems. It is domain contact and name server changes that have have caused the speculation. Many claim it resets the sites Google “trust points”. There are many influences on SERPs and SEO is always a moving target, so take this warning with a grain for salt. But I thought it was worth mentioning.
For More Information
DNS Wiki – http://en.wikipedia.org/wiki/Domainnamesystem
DNS Forum – http://member.dnsstuff.com/forums/
Web-based DNS Tools – http://www.dnstools.com/
DNS Surveys – http://www.seoconsultants.com/tools/dns/surveys/