Capital, and Sutter Hill Ventures. On August 27, 2015, Cisco acquired OpenDNS for in an all-cash transaction, plus retention-based incentives for OpenDNS. OpenDNS's business services were renamed Cisco Umbrella; home products retained the OpenDNS name. Cisco said that it intended to continue development of OpenDNS with its other cloud-based security products, and that it would continue its existing services. Discontinued advertising OpenDNS previously earned a portion of its revenue by resolving a domain name to an OpenDNS server when the name is not otherwise defined in DNS. This had the effect that if a user typed a non-existent name in a URL in a web browser, the user saw an OpenDNS search page. Advertisers paid 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. OpenDNS said that the advertising revenue paid for the free customized DNS service. It was discontinued on June 6, 2014; OpenDNS said this was because of their move towards a security focus in their business. Reception 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 that corrects mistyped addresses and redirects keyword addresses to OpenDNS's search page, while the rest is transparently passed through to the intended recipient. 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). Users can disable this behavior by logging into their OpenDNS account and unchecking "OpenDNS proxy" option; Mozilla users can instead install an extension, or change or remove the navclient sourceid from their keyword search URLs. This redirection breaks some non-Web applications that rely on getting an NXDOMAIN response for non-existent 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