Most DNS servers Speedy Fast and Precisely

Speedy .. You sounds speedy ... how could make susye .. Using DNS neighbors have consequently become a mess .. That's roughly the comment right after this problem solved. In this article we will seek control practices which are the most ideal Speedy installed in the router / server we.

Note This is still associated with a previous post. After my story on the dial via Router Mikrotik Speedy, Speedy episode turns out we are still continuing. This time there is a problem on the stability of Telkom's flagship product of this connection. Mikrotik router via a dial process already cepet like hope. Each time a direct dial connection mikrotik drop. But unfortunately the transfer speed charts weird, is not as stable as dial via modem. Not that slow, it's not clear even up and down. Ping from Mikrotik router to Yahoo it is not unusual for a timeout is not clear so ... More precisely let us trace back together ..

The first suspect this event falls on a LAN connection or installation mikrotik. But after the fall of the same investigation several times, even after I confirmed to the forum and read and read the blog.

The next allegation leads to speedy control. After back and forth almanac books DNS has ever given friends, finally I found a few rows of figures control.

To make sure, I checked the IP control that appears when done via dialup modem pake nslookup. 202.134.1.10 IP results indicate that this IP belongs to nssby1.telkom.net.id, DNS servers Telkom Surabaya. My next thoughts looking for DNS servers that are closer to my position, I try to search by keyword nssmg1.telkom.net.id, finally met the IP 203.130.208.18. Searching for the search led me to some of the IP telecom families following:

202.134.0.155 nsjkt1.telkom.net.id
202.134.0.62 dns1.telkom.net.id
Alias 203.130.196.5 dns2.telkom.net.id nsjkt2.telkom.net.id
202.134.1.10 nssby1.telkom.net.id
203.130.208.18 nssmg1.telkom.net.id

There are many sources of writing a post on the web about the IP control. Some say the control of Jakarta's most cepet 202.134.0.155. Some other sources say different things. Some even recommend non-speedy IP control, or put another DNS server owned by another company. To this I disagree, both in terms of legality, and speed (after going through the process a check).

Even if want pake control outside considerable mending pake cepet OpenDNS and it is totally free. I personally use this control on the client side as a secondary DNS, of course with primary-dns tetep have pake speedy. Just as a backup, the results are pretty good. Although more lemot of IP Telkom, OpenDNS rarely have time-outs. OpenDNS IP Here is what I mean:

208.67.220.220
208.67.222.222

Speedy Return to DNS, then I do ping and traceroute tests on a number of IP. After several test series, the most optimal results I get from the following servers, sequentially from the fastest to the slowest.

Semarang 203.130.208.18
202.134.0.62 DNS1
Surabaya 202.134.1.10

My temporary conclusion is that the optimal control is to control the use of its geographical position is closer to our position. I immediately thought of the statement speedy installation of telecom officer stating that the speed of each client's speedy results vary. One of them is influenced by the network installation and connectivity to the server.

If this is true, it means that basically there is no control that is faster than the lain.DNS the most appropriate alternative in certain circumstances, in accordance with the client's location of speedy and quality of the network. That there is

Finally, I can love not wearing the standard recommendation for other people to your connections. Others standards apply only if the same position with your position and the quality of your installation and connectivity at least equal, or better. If you want to optimize, do yourself a check with nslookup and ping to some IP control. Choose the best for your own connection ..

How? Agree? Just a reference, I add the following collection of control that you should try.

Service providers: Google
* 8.8.8.8
* 8.8.4.4

Service provider: ScrubIt
67.138.54.100 *
* 207.225.209.66

Service provider: dnsadvantage
* 156.154.70.1
* 156.154.71.1

Service provider: OpenDNS
* 208.67.222.222
* 208.67.220.220

209.244.0.3
209.244.0.4

Service Provider: OpenNIC
58.6.115.42 AU
58.6.115.43 AU
AU 119.31.230.42
BR 200.252.98.162
DE 217.79.186.148
FR 82,229,244,191
U.S. 216.87.84.211
U.S. 2002: d857: 54d2: 2:20 e: 2eff: fe63: d4a9
U.S. 2001:470:1 f07: 38b:: 1
U.S. 66.244.95.20
U.S. 2001:470:1 F10: c6:: second

141.211.125.17
141.211.144.17
198.77.116.8
198.77.116.12
198.77.116.221
198.77.116.223
198.77.116.225
198.77.116.227
205.171.2.65
205.171.3.65
141.211.144.15
Hopefully useful