3 ms·

While indeed slower then Google ones for example, like double the speed, still I would argue that it doesn't really change that much when you are loading the pa

While indeed slower then Google ones for example, like double the speed, still I would argue that it doesn't really change that much when you are loading the page. For most part, entries a cached locally and in single visit, you are not visiting more then one domain. I think we should welcome this line of thinking and acting, internet is becoming less free place every day. Not the same, but I was reading this article about a guy who is on Verizon and gets better Netflix when he uses his VPN.

rakoo 12y ago
> internet is becoming less free place every day. And DNS.watch isn't solving anything. It only moves your dependency from one third-party (your ISP, Google, OpenDNS) to another one (DNS.watch). If we really want to keep internet the way it was intended, we must run our own resolvers. That will most certainly defeat the cacheability of DNS but it is very much needed.
- pedrogpimenta 12y ago
  I like this idea. Any links as to how to build your own DNS resolver? I already have some things on my own "cloud", this would be one thing more :)
  - danyork 12y ago
    A great place to start would be to install Unbound - a great resolving caching server from NLNet Labs: http://unbound.net/ http://unbound.net/ They also have a version focused on providing DNSSEC validation called "DNSSEC-Trigger": http://www.nlnetlabs.nl/projects/dnssec-trigger/ http://www.nlnetlabs.nl/projects/dnssec-trigger/ Wikipedia also has a decent comparison of a wide range of different resolvers: https://en.wikipedia.org/wiki/Comparison_of_DNS_server_software https://en.wikipedia.org/wiki/Comparison_of_DNS_server_softw... The key is that in the "Feature matrix" table there you need to have a "Yes" in the "Recursive" column.
  - danyork 12y ago
    If you want to completely build your own DNS resolver, or integrate that functionality into an app, I would recommend looking at the new getDNS API: http://getdnsapi.net/ http://getdnsapi.net/ also on Github at: https://github.com/getdnsapi/getdns https://github.com/getdnsapi/getdns There are also a range of other DNS developer libraries out there. Here is a list of some: http://www.internetsociety.org/deploy360/resources/dnssec-developer-libraries/ http://www.internetsociety.org/deploy360/resources/dnssec-de...
- scott_karana 12y ago
  It doesn't defeat cacheability when you're doing it on routers or any other DHCP-shared LAN-only resolver; there's no reason you can't pool all your household devices on a dedicated caching resolver. OpenWRT/Tomato/etc provide "dnsmasq" for exactly this reason. :-)

rakoo 12y ago

> internet is becoming less free place every day. And DNS.watch isn't solving anything. It only moves your dependency from one third-party (your ISP, Google, OpenDNS) to another one (DNS.watch). If we really want to keep internet the way it was intended, we must run our own resolvers. That will most certainly defeat the cacheability of DNS but it is very much needed.

pedrogpimenta 12y ago
I like this idea. Any links as to how to build your own DNS resolver? I already have some things on my own "cloud", this would be one thing more :)
- danyork 12y ago
  A great place to start would be to install Unbound - a great resolving caching server from NLNet Labs: http://unbound.net/ http://unbound.net/ They also have a version focused on providing DNSSEC validation called "DNSSEC-Trigger": http://www.nlnetlabs.nl/projects/dnssec-trigger/ http://www.nlnetlabs.nl/projects/dnssec-trigger/ Wikipedia also has a decent comparison of a wide range of different resolvers: https://en.wikipedia.org/wiki/Comparison_of_DNS_server_software https://en.wikipedia.org/wiki/Comparison_of_DNS_server_softw... The key is that in the "Feature matrix" table there you need to have a "Yes" in the "Recursive" column.
- danyork 12y ago
  If you want to completely build your own DNS resolver, or integrate that functionality into an app, I would recommend looking at the new getDNS API: http://getdnsapi.net/ http://getdnsapi.net/ also on Github at: https://github.com/getdnsapi/getdns https://github.com/getdnsapi/getdns There are also a range of other DNS developer libraries out there. Here is a list of some: http://www.internetsociety.org/deploy360/resources/dnssec-developer-libraries/ http://www.internetsociety.org/deploy360/resources/dnssec-de...
scott_karana 12y ago
It doesn't defeat cacheability when you're doing it on routers or any other DHCP-shared LAN-only resolver; there's no reason you can't pool all your household devices on a dedicated caching resolver. OpenWRT/Tomato/etc provide "dnsmasq" for exactly this reason. :-)