Google Starts Own DNS Service: 22.214.171.124 and 126.96.36.199
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 188.8.131.52 nameserver 184.108.40.206
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.
MSBuild is now just another GitHub project as Redmond continues its path to the light.
New rules emphasize collegiality in coding.
Upstart lands in the dust bin as a new era begins for Linux.
HP's annual Cyber Risk report offers a bleak look at the state of IT.
But what do the big numbers really mean?
.NET Core execution engine is the basis for cross-platform .NET implementations.
The Xnote trojan hides itself on the target system and will launch a variety of attacks on command.
Spammers go low-volume, and 90% of IE browsers are unpatched.
Adobe scrambles to release patches for vulnerable Flash Player.