Google Starts Own DNS Service: 188.8.131.52 and 184.108.40.206
Google can't get enough of the Internet. Now the company is promoting its own nameserver service that it claims is not only faster than the usual DNS, but more secure.
Why use a public DNS server when there is Google? Using the simple entry in the /etc/resolve.conf file:
nameserver 220.127.116.11 nameserver 18.104.22.168
Linux users can forego their providers' name server and go directly to Google to resolve their IP addresses to domain names. Always up and guaranteed failure-proof and intrusion-safe, says Google. The service also fits quite well within their portfolio: everyone searching the Web for something can google it, why not also IP addresses? It also makes it easier for Google to log usage records, with the result that it will now know just about everything.
The idea of an own nameserver seems trivial, yet ingeniously simple and extremely dangerous. On the one hand it allows bypassing of ISP locks on the nameserver level, on the other hand Goggle can thereby build a central monopoly with a predisposition for censorship that goes way beyond what a search engine should be capable of doing.
Benefits of the new nameserver service, according to Google, are:
- Speed, via "clever caching" and record prefetching.
- Security, with mechanisms for preventing spoofing attacks.
- Validy, by eliminating blocking, filtering or redirection.
We are faster
As usual, Google's number one concern is speed. Users of the new Public DNS service should get much greater name resolution speeds than with the average DNS service, certainly palpable by Google's infrastructure and hopefully corroborated by some testing done before the official launch. Everyone should benefit, by Google's usual claim: "We plan to share what we learn from this experimental rollout of Google Public DNS with the broader web community and other DNS providers, to improve the browsing experience for Internet users globally."
Going it all alone
Google's number two concern has also been long evident: over the years DNS has shown certain opportunities for DNS spoofing and denial-of-service (DoS) attacks that haven't received enough attention. Work on it, mainly through DNSSEC, is being done, however. All the more surprising that a company like Google that has long been entrusted with the Internet's DNS structures is now providing its own DNS solution. It seems to be easier to promote one's own service than work together to make the classic DNS service more secure. Google will therewith not win many friends in the open source arena.
Mozilla’s product think tank sinks silently into history.
TODO group will focus on open source tools in large-scale environments.
New tool will look like GParted but support a wider range of storage technologies.
New public key pinning feature will help prevent man-in-the-middle attacks.
Carnegie Mellon researchers say 3 million pages could fall down the phishing hole in the next year.
The US government rolls new best-practice rules for protecting SSH.
Klaus Knopper announces the latest version of his iconic Live Linux system.
All websites that use these popular CMS tools could be vulnerable to denial of service attacks if users don't install the updates.
According to a report, many potential victims of the Heartbleed attack have patched their systems, but few have cleaned up the crime scene to protect themselves from the effects of a previous intrusion.
DARPA and NICTA release the code for the ultra-secure microkernel system used in aerial drones.