Un bloqueo masivo amenaza las redes P2P y las descargas directas en Europa

Claudio Valero | 16 de Abril 2013 | 20:00 34 comentarios El Gobierno italiano ha decidido bloquear unas 30 pginas web relacionadas con el intercambio de ficheros P2P y con las descargas directas. Entre ellas, Rapidgator, Uploaded, NowVideo, VideoPremium y Uploaded. La cosa no va a quedar ah, ya que quieren continuar el caso a nivel internacional, lo que podra acabar con un bloqueo masivo de dominios. Segn podemos leer en Alt1040, el Gobierno italiano ha decidido bloquear varias pginas web de intercambio de ficheros P2P y de descarga directa. La operacin se ha bautizado como Un monstruo de Roma, bastante acertado viendo las consecuencias que ha tenido. La fiscala de Roma ha actuado contra 27 pginas web dedicadas al intercambio de ficheros. Esta es la segunda operacin ms grande de este tipo despus de la realizada por la Agencia de Seguridad Nacional de Estados Unidos en 2010. En esta operacin se bloquearon ms de 70 pginas web en total. Las web bloqueadas por el Gobierno italiano son inaccesibles desde todo el pas. La fiscala de Roma ha anunciado que esto no quedar aqu y quieren llevar el caso a nivel internacional, para conseguir un bloqueo completo. Los abogados expertos en la materia se han mostrado muy preocupados por los acontecimientos y temen lo que podra llegar a pasar en un futuro. Suponemos que detrs de estas acciones estar la industria cinematogrfica y musical, presionando para lograr el cierre de estas pginas web y jugando con algo tan delicado como la libertad de expresin. No olvidemos que estos servicios de descarga directa pueden alojar ficheros de particulares sin derechos de autor, algo que parece que siempre se deja de lado en estos casos. El bloqueo se ha realizado a nivel de DNS y ya existen algunos usuarios que estn logrando saltrselo. Para ello, deben cambiar las DNS de su proveedor de Internet por otras, como las de OpenDNS o las de Google. Con este cambio, los internautas italianos pueden volver a acceder a las pginas bloqueadas. Una amenaza censora se cierne sobre el continente europeo despus del cierre de varias pginas web en Italia. Esperemos que no comience a extenderse esta prctica por ms pases. Qu opinis del bloqueo llevado a cabo en Italia?

What is Google Public DNS?

Google Public DNS is a free, global Domain Name System (DNS) resolution service, that you can use as an alternative to your current DNS provider. To try it out:

Configure your network settings to use the IP addresses 8.8.8.8 and 8.8.4.4 as your DNS servers or Read our configuration instructions (IPv6 addresses supported too).

If you decide to try Google Public DNS, your client programs will perform all DNS lookups using Google Public DNS.

Why does DNS matter?

The DNS protocol is an important part of the web's infrastructure, serving as the Internet's phone book: every time you visit a website, your computer performs a DNS lookup. Complex pages often require multiple DNS lookups before they start loading, so your computer may be performing hundreds of lookups a day.

Why should you try Google Public DNS?

By using Google Public DNS you can:

Speed up your browsing experience. Improve your security. Get the results you expect with absolutely no redirection.

Using Google Public DNS

Download this page in PDF

Configuring your network settings to use Google Public DNS Testing your new settings Diagnosing resolution problems Switching back to your old DNS settings

Configuring your network settings to use Google Public DNS

When you use Google Public DNS, you are changing your DNS "switchboard" operator from your ISP to Google Public DNS. In most cases, the IP addresses used by your ISP's domain name servers are automatically set by your ISP via the Dynamic Host Configuration Protocol (DHCP). To use Google Public DNS, you need to explicitly change the DNS settings in your operating system or device to use the Google Public DNS IP addresses. The procedure for changing your DNS settings varies according to operating system and version (Windows, Mac or Linux) or the device (computer, phone, or router). We give general procedures here that might not apply for your OS or device; please consult your vendor documentation for authoritative information. Note: We recommend that only users who are proficient with configuring operating system settings make these changes.

Important: Before you start

Before you change your DNS settings to use Google Public DNS, be sure to write down the current server addresses or settings on a piece of paper. It is very important that you keep these numbers for backup purposes, in case you need to revert to them at any time.

After changing your settings, if you encounter a problem and cannot connect to the Internet, please call our support numbers for troubleshooting instructions. We also recommend that you download this page and print it, in the event that you encounter a problem and need to refer to these instructions. Google Public DNS telephone support

877-590-4367 in the U.S. 770-200-1201 outside the U.S.

Google Public DNS IP addresses

The Google Public DNS IP addresses (IPv4) are as follows:

8.8.8.8 8.8.4.4

The Google Public DNS IPv6 addresses are as follows:

2001:4860:4860::8888 2001:4860:4860::8844

You can use either number as your primary or secondary DNS server. You can specify both numbers, but do not specify one number as both primary and secondary. You can configure Google Public DNS addresses for either IPv4 or IPv6 connections, or both.

Changing your DNS servers settings

Because the instructions differ between different versions/releases of each operating system, we only give one version as an example. If you need specific instructions for your operating system/version, please consult your vendor's documentation. You may also find answers on our user group. Many systems allow you to specify multiple DNS servers, to be contacted in a priority order. In the following instructions, we provide steps to specify only the Google Public DNS servers as the primary and secondary servers, to ensure that your setup will correctly use Google Public DNS in all cases. Note: Depending on your network setup, you may need administrator/root privileges to change these settings. Microsoft Windows DNS settings are specified in the TCP/IP Properties window for the selected network connection. Example: Changing DNS server settings on Microsoft Windows 7 1. Go the Control Panel. 2. Click Network and Internet, then Network and Sharing Center, and click Change adapter settings. 3. Select the connection for which you want to configure Google Public DNS. For example: o To change the settings for an Ethernet connection, right-click Local Area Connection, and click Properties. o To change the settings for a wireless connection, right-click Wireless Network Connection, and click Properties.

If you are prompted for an administrator password or confirmation, type the password or provide confirmation. 4. Select the Networking tab. Under This connection uses the following items, select Internet Protocol Version 4 (TCP/IPv4) or Internet Protocol Version 6 (TCP/IPv6) and then click Properties. 5. Click Advanced and select the DNS tab. If there are any DNS server IP addresses listed there, write them down for future reference, and remove them from this window. 6. Click OK. 7. Select Use the following DNS server addresses. If there are any IP addresses listed in the Preferred DNS server or Alternate DNS server, write them down for future reference. 8. Replace those addresses with the IP addresses of the Google DNS servers: o For IPv4: 8.8.8.8 and/or 8.8.4.4. o For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 9. Restart the connection you selected in step 3. 10. Test that your setup is working correctly; see Testing your new settings below. 11. Repeat the procedure for additional network connections you want to change. Mac OS X DNS settings are specified in the Network window. Example: Changing DNS server settings on Mac OS 10.5 1. From the Apple menu, click System Preferences, then click Network. 2. If the lock icon in the lower left-hand corner of the window is locked, click the icon to make changes, and when prompted to authenticate, enter your password. 3. Select the connection for which you want to configure Google Public DNS. For example: o To change the settings for an Ethernet connection, select Built-In Ethernet, and click Advanced. o To change the settings for a wireless connection, select Airport, and click Advanced. 4. Select the DNS tab. 5. Click + to replace any listed addresses with, or add, the Google IP addresses at the top of the list: o For IPv4: 8.8.8.8 and/or 8.8.4.4. o For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 6. Click Apply and OK. 7. Test that your setup is working correctly; see Testing your new settings below. 8. Repeat the procedure for additional network connections you want to change. Linux In most modern Linux distributions, DNS settings are configured through Network Manager. Example: Changing DNS server settings on Ubuntu 1. In the System menu, click Preferences, then click Network Connections. 2. Select the connection for which you want to configure Google Public DNS. For example: o To change the settings for an Ethernet connection, select the Wired tab, then select your network interface in the list. It is usually called eth0. o To change the settings for a wireless connection, select the Wireless tab, then select the appropriate wireless network. 3. Click Edit, and in the window that appears, select the IPv4 Settings or IPv6 Settings tab. 4. If the selected method is Automatic (DHCP), open the dropdown and select Automatic (DHCP) addresses only instead. If the method is set to something else, do not change it. 5. In the DNS servers field, enter the Google Public DNS IP addresses, separated by a space:

For IPv4: 8.8.8.8 and/or 8.8.4.4. For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 6. Click Apply to save the change. If you are prompted for a password or confirmation, type the password or provide confirmation. 7. Test that your setup is working correctly; see Testing your new settings below. 8. Repeat the procedure for additional network connections you want to change. If your distribution doesn't use Network Manager, your DNS settings are specified in /etc/resolv.conf. Example: Changing DNS server settings on a Debian server 1. Edit /etc/resolv.conf:
sudo vi /etc/resolv.conf

o o

2. If any nameserver lines appear, write down the IP addresses for future reference. 3. Replace the nameserver lines with, or add, the following lines: For IPv4:
nameserver 8.8.8.8 nameserver 8.8.4.4

For IPv6:
nameserver 2001:4860:4860::8888 nameserver 2001:4860:4860::8844

4. Save and exit. 5. Restart any Internet clients you are using. 6. Test that your setup is working correctly; see Testing your new settings below. Additionally, if you are using DHCP client software that overwrites the settings in /etc/resolv.conf, you will need to set up the client accordingly by editing the client's configuration file. Example: Configuring DHCP client sofware on a Debian server 1. Back up /etc/resolv.conf:
sudo cp /etc/resolv.conf /etc/resolv.conf.auto

2. Edit /etc/dhcp3/dhclient.conf:
sudo vi /etc/dhcp3/dhclient.conf

3. If there is a line containing domain-name-servers, write down the IP addresses for future reference. 4. Replace that line with, or add, the following line: For IPv4:
prepend domain-name-servers 8.8.8.8, 8.8.4.4;

For IPv6:
prepend domain-name-servers 2001:4860:4860::8888, 2001:4860:4860::8844;

5. Save and exit. 6. Restart any Internet clients you are using. 7. Test that your setup is working correctly; see Testing your new settings below. Routers Every router uses a different user interface for configuring DNS server settings; we provide only a generic procedure below. For more information, please consult your router documentation. Note: Some ISPs hard-code their DNS servers into the equipment they provide; if you are using such a device, you will not be able to configure it to use Google Public DNS. Instead, you can configure each of the computers connected to the router, as described above. To change your settings on a router: 1. 2. 3. 4. 5. In your browser, enter the IP address to access the router's administration console. When prompted, enter the password to access network settings. Find the screen in which DNS server settings are specified. If there are IP addresses specified in the fields for the primary and seconday DNS servers, write them down for future reference. Replace those addresses with the Google IP addresses: o For IPv4: 8.8.8.8 and/or 8.8.4.4. o For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 Save and exit. Restart your browser. Test that your setup is working correctly; see Testing your new settings below.

6. 7. 8.

Mobile or other devices DNS servers are typically specified under advanced wi-fi settings. However, as every mobile device uses a different user interface for configuring DNS server settings, we provide only a generic procedure below. For more information, please consult your mobile provider's documentation. To change your settings on a mobile device: 1. Go to the screen in which wi-fi settings are specified. 2. Find the screen in which DNS server settings are specified. 3. If there are IP addresses specified in the fields for the primary and seconday DNS servers, write them down for future reference. 4. Replace those addresses with the Google IP addresses: o For IPv4: 8.8.8.8 and/or 8.8.4.4. o For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 5. Save and exit. 6. Test that your setup is working correctly; see Testing your new settings below.

Testing your new settings

To test that the Google DNS resolver is working: 1. From your browser, type in a hostname (such as http://www.google.com/). If it resolves correctly, bookmark the page, and try accessing the page from the bookmark. If both of these tests work, everything is working correctly. If not, go to step 2. 2. From your browser, type in a fixed IP address. You can use http://18.62.0.96/ (which points to the website http://www.eecs.mit.edu/) as the URL*. If this works correctly, bookmark the page, and try accessing the page from the bookmark. If these tests work (but step 1 fails), then there is a

problem with your DNS configuration; check the steps above to make sure you have configured everything correctly. If these tests do not work, go to step 3. 3. Roll back the DNS changes you made and run the tests again. If the tests still do not work, then there is a problem with your network settings; contact your ISP or network administrator for assistance. * Google thanks MIT for granting permission to use this URL for the purposes of testing web connectivity.

Diagnosing resolution problems

If you are encountering problems when resolving particular names, and want to verify whether the problem is with Google Public DNS, please try running the following diagnostic procedures. If you want to report a problem to the Google Public DNS user group, please copy and paste the results of the commands in your email. This information is vital to help us to identify the cause of the problem.

Step 1: Verify that your client can communicate with the Google Public DNS servers
IPv4 Open a command prompt, and run the following command: On Windows:
tracert -d 8.8.8.8

On Mac OS X:
/usr/sbin/traceroute -n -w 2 -q 2 -m 30 8.8.8.8

On Linux:
sudo traceroute -n -w 2 -q 2 -m 30 8.8.8.8

If the last line of the output does not list 8.8.8.8 as the final hop, or if there are significant timeouts, there may be a network problem preventing you from contacting our servers. Please include the output of the command in any communication with the Google Public DNS team. If the last line of the output does list 8.8.8.8 as the final hop, continue to step 2. IPv6 Open a command prompt, and run the following command: On Windows:
tracert -d 2001:4860:4860::8888

On Mac OS X:
/usr/sbin/traceroute6 -n -w 2 -q 2 -m 30 2001:4860:4860::8888

On Linux:
sudo traceroute -n -w 2 -q 2 -m 30 2001:4860:4860::8888

If the last line of the output does not list 2001:4860:4860::8888 as the final hop, or if there are significant timeouts, there may be a network problem preventing you from contacting our servers. Try configuring Google Public DNS for IPv4 to diagnose whether the problem is due to IPv6 connectivity on your network. If IPv4 works for you, you may want to revert your IPv6 configuration and use Google Public DNS with IPv4 exclusively. Otherwise, please include the output of the command in any communication with the Google Public DNS team. If the last line of the output does list 2001:4860:4860::8888 as the final hop, continue to step 2.

Step 2: Verify that Google Public DNS can resolve the selected hostname
IPv4 At the command prompt, run the following command, replacing www.google.com. with the name that you were having difficulty resolving (putting a period at the end of the name to avoid problems with domain suffixes and search lists): On Windows:
nslookup -debug www.google.com. 8.8.8.8

On Mac and Linux:

dig @8.8.8.8 www.google.com.

If the output shows an answer section with an A record for the hostname, then Google Public DNS is able to resolve the name. Check your settings to make sure your system is correctly configured to use Google Public DNS. If you are still unable to solve the problem, please include the output of the command in any communication with the Google Public DNS team. If the output does not show an answer for the hostname, continue to step 3. IPv6
Windows

At the command prompt, run the following command, replacing www.google.com. with the name that you were having difficulty resolving* (putting a period at the end of the name to avoid problems with domain suffixes and search lists):
nslookup -debug -type=AAAA www.google.com. 2001:4860:4860::8888

If the output shows an answer section with an AAAA record for the hostname, then Google Public DNS is able to resolve the name. Check your settings to make sure your system is correctly configured to use Google Public DNS. If you are still unable to solve the problem, please include the output of the command in any communication with the Google Public DNS team. If the output shows an answer section with an A (IPv4) record for the hostname, then Google Public DNS is able to resolve the name, but the host and/or its nameserver are not configured to return IPv6 results. If you want to verify that you are correctly receiving AAAA records, you can use the hostname ipv6.google.com as a generic test. If the output for ipv6.google.com, or another host for which you are certain IPv6 records exist, does not show an answer, continue to step 3.

On Mac and Linux

At the command prompt, run the following command, replacing www.google.com. with the name that you were having difficulty resolving*. (putting a period at the end of the name to avoid problems with domain suffixes and search lists):
dig @2001:4860:4860::8888 www.google.com. AAAA

If the output shows an answer section with an AAAA record for the hostname, then Google Public DNS is able to resolve the name. Check your settings to make sure your system is correctly configured to use Google Public DNS. If you are still unable to solve the problem, please include the output of the command in any communication with the Google Public DNS team. If the output does not show an AAAA record for the hostname, this may be because the the host and/or its nameserver are not configured to return IPv6 results. If you want to verify that you are correctly receiving AAAA records, you can use the hostname ipv6.google.com as a generic test. If the output for ipv6.google.com, or another host for which you are certain IPv6 records exist, does not show an answer, continue to step 3. *Note: Google properties will not return AAAA records for all users. Please see the Google over IPv6 page for more information about whether your system qualifies.

Step 3: Verify that another open resolver can resolve the selected hostname
At the command prompt, run any one of the following commands, replacing www.google.com. with the name that you were having difficulty resolving (still putting a period at the end of the name to avoid problems with domain suffixes and search lists):
nslookup nslookup nslookup nslookup www.google.com. www.google.com. www.google.com. www.google.com. 4.2.2.1 4.2.2.2 208.67.222.222 208.67.220.220

(The first two commands test Level 3's DNS servers. The last two commands test OpenDNS' DNS servers.) If you are not able to get a successful result, this means that there is most likely a problem with the server you are trying to contact. Wait some time and try running the tests again. This may be a temporary problem on the server's side that will likely resolve itself eventually. If it does not, you should contact the owner of the server. If you do get a successful result, there may be a problem with Google Public DNS. Please include the output of this command and the one from step 2 in any communication with the Google Public DNS team.

Step 4: Check to see if the authoritative nameservers are correct

If Google Public DNS (or any open resolver) has trouble resolving a site, or returns inconsistent answers, sometimes it's because the authoritative nameservers are having trouble. There are various tools and sites to help you check this. Some users (and some Google Public DNS engineers) have found intoDNS to be very helpful. For example, if you're trying to resolve www.example.com, visit intodns.com and enter example.com (the domain for www.example.com), or visit http://intodns.com/example.com directly. Google thanks the intoDNS staff for letting us link to them.

Switching back to your old DNS settings

If you had not previously configured any customized DNS servers, to switch back to your old settings, in the window in which you specified the Google IP addresses, select the option to enable obtaining DNS server addresses automatically, and/or delete the Google IP addresses. This will revert your settings to using your ISP's default servers. If you need to manually specify any addresses, use the procedures above to specify the old IP addresses. If necessary, restart your system. Last updated November 5, 2012.

Google Public DNS

[1]

is a freely provided DNS (Domain Name System) service announced on 3 December 2009, as part of Google's self-proclaimed effort to make the web faster.[2][3] According to Google, as of 2013 Google Public DNS is the largest public DNS service in the world, handling more than 130 billion requests on an average day.[4] Google Public DNS provides the following recursive nameserver addresses for public use,[5] mapped to the nearest operational server location by anycast routing:[6] IPv4 addresses

8.8.8.8 8.8.4.4

IPv6 addresses[7]

2001:4860:4860::8888 2001:4860:4860::8844

Services
The service does not use third party DNS management software such as BIND, instead relying on a custombuilt implementation, with limited IPv6 support, conforming to the DNS standards set forth by the IETF. It fully supports the DNSSEC protocol since 19 March, 2013 (previously Google Public DNS accepted and forwarded DNSSEC-formatted messages but did not perform validation).[8] [9] Many popular DNS providers practice DNS hijacking while processing queries, causing web browsers to redirect to an advertisement site run by the provider when a nonexistent domain name is entered, explicitly breaking the DNS specification.[10] In contrast, Google's service correctly replies with an NXDOMAIN (non-existing domain)[11] code in this situation, and this feature alone is cited by many new users to justify switching.[12] Google also specifically addresses the security of Domain Name Serving, whereby third parties interfere with a DNS service to try to redirect users from legitimate to malicious websites. They document their efforts to be resistant to DNS cache poisoning including "Kaminsky Flaw" attacks as well as Denial-ofservice attacks.[13] Google claims various efficiency and speed benefits,[14] such as using anycast routing to send users to the closest worldwide data center, overprovisioning servers to handle even malicious traffic, and load-balancing servers using two cache levels, with a small per-machine cache containing the most popular names and another pool of machines partitioned by the name to be looked up. This second level cache reduces the fragmentation and cache miss rate that can result from just increasing the number of servers.

Privacy
It is stated that for the purposes of performance and security, only the user's IP address (deleted after 24 hours), ISP, and location information (kept permanently) are stored on the servers.[15][16][17]

History
In December 2009, Google Public DNS was launched with its announcement[18] on the Official Google Blog by product manager Prem Ramaswami, with an additional post on the Google Code blog.[19] On January 28 2013, Google's DNS servers silently started providing DNSSEC validation information,[20] setting the AD flag in their answers when resolvers ask for it (by setting the DO flag in their queries). Until then, RRSIG records were provided but the AD flag was never set.
Official "Google Public DNS" Product Website

OpenDNS extends DNS (Domain Name System) adding features such as misspelling correction,

phishing protection, and optional content filtering. It provides an ad-supported service[1] "showing relevant ads when we [show] search results" and a paid advertisement-free service. The companys Umbrella cloud-delivered security service secures enterprise users from malware, botnets and phishing on PCs, laptops, and iOS devices. The OpenDNS Global Network processes ~45 billion DNS queries daily from 50 million active users connected to the service through 19 data centers worldwide.[2]

Services
DNS
OpenDNS offers DNS resolution as an alternative to using Internet service providers' DNS servers. There are OpenDNS servers in strategic locations, and they also employ a large cache of the domain names.[citation needed] OpenDNS has adopted and supports DNSCurve.[3] OpenDNS provides the following recursive nameserver addresses[4] for public use, mapped to the nearest operational server location by anycast routing:

208.67.222.222 (resolver1.opendns.com) 208.67.220.220 (resolver2.opendns.com) 208.67.222.220 [4] 208.67.220.222 [4]

IPv6 addresses (experimental)[5]

2620:0:ccc::2 2620:0:ccd::2

Other features include a phishing filter, domain blocking and typo correction (for example, typing "example.og" instead of "example.org"). OpenDNS maintains a list of malicious sites and blocks access to them when a user tries to access them through their service. OpenDNS also run a service called PhishTank for users to submit and review suspected phishing sites.

The name OpenDNS refers to the DNS concept of being open, where queries from any source are accepted. It is not related to open source software; the service is based on closed-source software.[6] OpenDNS earns a portion of its revenue by resolving a domain name to an OpenDNS server when the name is not otherwise defined in DNS. This has the effect that if a user types a non-existent name in a URL in a web browser, the user sees an OpenDNS search page. Advertisers pay OpenDNS to have advertisements for their sites on this page. This behavior is similar to VeriSign's previous Site Finder or the redirects many ISP's place on their own DNS servers, but it is a service provided only at users' request.[7] OpenDNS says that the advertising revenue pays for the free customized DNS service.[8] As of March 2010 OpenDNS said that it handled over 20 billion DNS requests daily, with over 26 billion delivered on 21 April 2010.[9] OpenDNS may have negligible performance gain,[10] but may process queries more quickly than an ISP with slow DNS servers.[11] DNS query results are sometimes cached by routers (e.g. typically local ISPs queries may be cached by ISPs home routers), the local operating system or applications, so speeds may not be noticeable with every request but only with requests that are not stored in a local cache.

DNS rebinding protection

To provide protection against DNS rebinding, private IP addresses can be (optionally) filtered out of DNS responses.[12]

Domain-blocking
On May 13, 2007, OpenDNS launched a domain-blocking service to block or filter web sites visited based upon categories, allowing control over the type of sites that may be accessed. The filters can be overridden through individually managed blacklists and whitelists. In 2008 OpenDNS changed from a closed list of blocked domains to a community-driven list allowing subscribers to suggest sites for blocking; if enough subscribers (the number has not been disclosed) concur with the categorization of the site it is added to the appropriate category for blocking. As of 2011 there were over 50 categories. The basic OpenDNS service does not require users to register, but using the block/filter feature requires registering and logging in.[13]

FamilyShield
OpenDNS also provides the following recursive nameserver addresses as part of their FamilyShield[14] parental controls which block pornography, proxy servers, phishing sites and some malware:

208.67.222.123 208.67.220.123

DNSCrypt
DNSCrypt is an implementation of DNSCurve, which encrypts DNS traffic between the user's computer and the OpenDNS name servers for Windows, Linux, Mac OS X and iPhone.[15]

Dynamic DNS
On December 3, 2007, OpenDNS began offering the free DNS-O-Matic service to provide a method of sending dynamic DNS (DDNS) updates to several DDNS providers using DynDNS's update API.[16]

OpenDNS Premium

On October 21, 2009, OpenDNS launched premium services. For a charge, the service offers ad-free result pages, increased reporting and block features, and other services.

Umbrella
On November 13, 2012 OpenDNS launched its enterprise security brand. Umbrella is designed to extend security to nomadic workers who roam beyond the corporate network using mobile devices such as iPhones, iPads, Windows and Mac laptops, and provide granular network security for distributed offices, retail locations and Wi-Fi hotspots. IT administrators can use its cloud-based management dashboard to define policies, provision devices, and view reports across users, sites, networks, groups, and devices.

History
July 2006 OpenDNS was launched by computer scientist and entrepreneur David Ulevitch. It received venture capital funding from Minor Ventures, which is led by CNET founder Halsey Minor. July 10, 2006 The service was covered by digg, Slashdot, and Wired News, which resulted in an increase of DNS requests from just over one million requests on July 9 to 30 million on July 11.[citation needed] October 2, 2006 OpenDNS launched PhishTank, an online collaborative anti-phishing database. Before 2007 OpenDNS was using the DNS Update API from DynDNS to handle updates from users with dynamic IPs.[17] June 11, 2007 OpenDNS started advanced web filtering to optionally block adult content for their free accounts. November 5, 2008 Nand Mulchandani, former head of VMware's security group, left VMware to join OpenDNS as new CEO, replacing founder David Ulevitch, who remained as the company's chief technology officer.[18] July 2009 OpenDNS was funded by Sequoia Capital and Greylock.[19] November, 2009 David Ulevitch resumed his post as CEO of OpenDNS. June 2010 OpenDNS launched "FamilyShield", a service designed to filter out sites with pornographic content. The service uses the DNS addresses 208.67.222.123 and 208.67.220.123.[20] September 1, 2010 The World Economic Forum announced the company as a Technology Pioneer for 2011.[21] November 8, 2011 Founder and CEO David Ulevitch wrote an open letter to Congress about the Stop Online Piracy Act and the Protect IP Act.[22]

Issues, conflicts and Google redirection

While the OpenDNS name resolution service is free, people have complained about how the service handles failed requests. If a domain cannot be found, the service redirects users to a search page with search results and advertising unless the user has paid for an upgraded service. Users can switch this off via the OpenDNS Control Panel, or specify another page to use for missing domains. This behavior is similar to that of many large ISPs who also redirect failed requests to their own servers containing advertising.[23] In 2007, David Ulevitch explained that in response to Dell installing "Browser Address Error Redirector" software on their PCs, OpenDNS started resolving requests to Google.com. Some of the traffic is handled by OpenDNS typo-correcting service which corrects mistyped addresses and redirects keyword addresses to OpenDNS's search page, while the rest is transparently passed through to the intended recipient.[24]

Also, a user's search request from the address bar of a browser that is configured to use the Google search engine (with a certain parameter configured) may be covertly redirected to a server owned by OpenDNS (which is within the OpenDNS Terms of Service).[25] Users can disable this behavior by logging in to their OpenDNS account and unchecking "OpenDNS proxy" option.[26] Additionally, Mozilla users can fix this problem by installing an extension[27] or by simply changing or removing the navclient sourceid from their keyword search URLs. This redirection breaks some non-Web applications that rely on getting an NXDOMAIN response for nonexistent domains, such as e-mail spam filtering, or VPN access where the private network's nameservers are consulted only when the public ones fail to resolve. Breaking local name resolution can be avoided by configuring the DNS addresses only in the forwarders of the local DNS server or router (the WAN/Internet configuration of a router or other gateway). For other purposes, or when the DNS addresses cannot be configured in a forwarder, domains for which an NXDOMAIN response is expected should be added to the Exceptions for VPN Users section of the OpenDNS Dashboard.

Server locations
Servers are located:[9]

Amsterdam, The Netherlands Chicago, Illinois, USA Dallas, Texas, USA Frankfurt, Germany London, United Kingdom Los Angeles, California, USA Miami, Florida, USA New York, New York, USA Palo Alto, California, USA Seattle, Washington, USA Singapore Washington, DC, USA Hong Kong, China

See also

Google Public DNS Norton DNS DNS Advantage

References
1. ^ July 26, 2007 (2007-07-26). "OpenDNS is a free, ad-based service". Pcmag.com. Retrieved 201108-21. 2. ^ "Open DNS System - current status of servers". Retrieved 2013-1-18. 3. ^ "OpenDNS adopts DNSCurve, official OpenDNS blog entry". Blog.opendns.com. Retrieved 201108-21. 4. ^ a b c "OpenDNS > Support > Knowledge Base > Additional (3rd and 4th) OpenDNS Addresses". OpenDNS. Retrieved 2011-09-21. 5. ^ OpenDNS IPv6 Sandbox 6. ^ OpenDNS | 0x80 7. ^ "OpenDNS knowledge base: OpenDNS is not like Site Finder". Opendns.com. Archived from the original on March 29, 2010. Retrieved 2010-04-20. 8. ^ "OpenDNS knowledge base: How does OpenDNS make money?". Opendns.com. Retrieved 201004-20.

9. ^ a b "OpenDNS stats". OpenDNS. 2012-02-17. Retrieved 2012-02-19. 10. ^ "OpenDNS Review & Rating PCMag.com". pcmag.com. 2007-07-26. Retrieved 2012-02-20. 11. ^ "OpenDNS: What's Your Take?". Neowin.net. 2007-03-13. Retrieved 2010-04-20. 12. ^ opendns 13. ^ "How to Protect your Kids Online using OpenDNS". PCTechNotes. 2009-03-17. Retrieved 201108-22. 14. ^ "OpenDNS Parental Controls". OpenDNS. Retrieved 2011-11-08. 15. ^ "Encrypt Dns Traffic In Linux With Dnscrypt (Via Opendns)". www.webupd8.org. 2012-02-17. Retrieved 2012-02-19. 16. ^ "OpenDNS Announces DNS-O-Matic: Free Service to Simplify Residential ISP and Small Businesses' Dynamic DNS Service". Prweb.com. Retrieved 2010-04-20. 17. ^ "Dynamic IP: General Info". OpenDNS. Retrieved 2010-04-20. 18. ^ "VMware security chief leaves to run OpenDNS". Computerworld.com.au. 2008-11-21. Retrieved 2010-04-20. 19. ^ Arrington, Michael. "Sequoia, Greylock Take Stake In OpenDNS", TechCrunch, July 7, 2009, accessed February 4, 2011. 20. ^ "Introducing FamilyShield Parental Controls". OpenDNS. 2010-06-23. Retrieved 2010-09-19. 21. ^ Thirty-One Visionary Companies Selected as Technology Pioneers 2011 22. ^ Open Letter from OpenDNS to Congress about SOPA and PROTECT IP 23. ^ http://nxr-opt-out-trial.comcast.net/ Comcast Domain Helper Service 24. ^ David Ulevitch. OpenDNS Blog Google turns the page... in a bad way. May 22, 2007. Retrieved 2008-07-04. 25. ^ Amit Agarwal Prevent OpenDNS from Redirecting Google Search Queries, March 21, 2008, Digital Inspiration. labnol.org. Retrieved 2008-07-04. 26. ^ "Is OpenDNS running a proxy?". Opendns.com. 2009-03-17. Retrieved 2011-10-09. 27. ^ I'm Feeling Lucky Problem Fix for OpenDNS users, July 3, 2008.

External links

OpenDNS website Dark Reading: OpenDNS Goes Mobile Nov. 15, 2012 PC World: OpenDNS introduces VPN, content filtering for mobile devices Nov. 13, 2012 PC Magazine: OpenDNS Extends Company Security to Mobile Devices Nov. 13, 2012