opennic:tier2

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		 Previous revision
Next revisionBoth sides next revision
opennic:tier2 [2017-04-19T04:34:01Z] – created jonaharagonopennic:tier2 [2017-09-20T10:09:50Z] – [Can I run it from home?] fusl
Line 7: Line 7:
 Tier 2 servers are "DNS Resolvers" or, servers that actually do the heavy-lifting when querying OpenNIC's DNS infrastructure. These are the servers that **clients use in their configuration** directly, and they provide access to the network. Anybody can operate a Tier 2 server, but there is a large amount of "Public Tier 2" servers to choose from at [[http://servers.opennicproject.org/|servers.opennicproject.org]]. Tier 2 servers are "DNS Resolvers" or, servers that actually do the heavy-lifting when querying OpenNIC's DNS infrastructure. These are the servers that **clients use in their configuration** directly, and they provide access to the network. Anybody can operate a Tier 2 server, but there is a large amount of "Public Tier 2" servers to choose from at [[http://servers.opennicproject.org/|servers.opennicproject.org]].
  
-Once you choose a server, you can setup your computers, phones, and all your other devices by following the guides at [[setup:start|the setup guides]].+Once you choose a server, you can setup your computers, phones, and all your other devices by following the guides at [[tier2setup|the setup guides]].
  
 ===== Who Runs the Tier 2 Servers? ===== ===== Who Runs the Tier 2 Servers? =====
Line 23: Line 23:
 We don't recommend you run it from a home connection, unless you have a high bandwidth and **low latency connection** with no bandwidth caps. Low WAN latency is important for running a DNS server, because the server itself is in charge of lookups, and high latency (e.g. on a home connection) can slow down requests dramatically compared to a server hosted with a low-latency connection in a datacenter. This graphic is a vast oversimplification of the DNS process but demonstrates why hosting at home is rarely a good idea: We don't recommend you run it from a home connection, unless you have a high bandwidth and **low latency connection** with no bandwidth caps. Low WAN latency is important for running a DNS server, because the server itself is in charge of lookups, and high latency (e.g. on a home connection) can slow down requests dramatically compared to a server hosted with a low-latency connection in a datacenter. This graphic is a vast oversimplification of the DNS process but demonstrates why hosting at home is rarely a good idea:
  
-{{ :opennic:latency.png?nolink&600 |}}+{{:opennic:tier2:latency_local.png|}}{{:opennic:tier2:latency_remote.png|}}
  
 The first graphic is an example of a Tier 2 server hosted at home. It needs to make numerous requests to "[[opennic:tier1|Authoritative]]" DNS servers, which are slowed down by the latency of the home connection. The second graphic has a higher latency between the user and the Tier 2 server, because it's outside the LAN, but the speed increases when communicating with Authoritative servers create a faster experience overall. The first graphic is an example of a Tier 2 server hosted at home. It needs to make numerous requests to "[[opennic:tier1|Authoritative]]" DNS servers, which are slowed down by the latency of the home connection. The second graphic has a higher latency between the user and the Tier 2 server, because it's outside the LAN, but the speed increases when communicating with Authoritative servers create a faster experience overall.
  • /wiki/data/pages/opennic/tier2.txt
  • Last modified: 7 years ago
  • by fusl