- Comodo uses strategically placed nodes are located at the most optimal intersections of the Internet. Unlike most DNS providers, the Comodo our request routing technology means that no matter where you are located in the world, your DNS requests are answered by the closest available set of servers, resulting in information becoming available faster and more reliably than ever before.]

I’m just wondering how COMODO DNS makes your Internet Browsing fast if your ISP’s DNS has a better LATENCY than COMODO DNS? attached here is a last week’s screenshots of my ISP’s DNS that outperforms COMODO DNS


[attachment deleted by admin]

In the past, I don’t know whether that is still the case, f.e. US cable companies had a downright below standards DNS support. In such cases switching to Comodo DNS, Open DNS etc can be a solution when it comes to performance.

Well on my case, I used COMODO DNS for a added security that I believed. BUT… I dough Comodo DNS makes my Internet fast because, the lower the PING, the fastest connection you well acquire and it is very clear here on my screenshot that Comodo DNS achieves above 200ms compare to my below 100ms ping result of my ISP’s DNS.


Since you’re looking at a difference of only 1/10th of a second between the two DNS services, do you really perceive any difference in your browsing experience?

This is what I find entertaining about most DNS discussions. Unless you’re using a DNS service that is really bad, any speed improvements you notice are really just in your head, as humans are very fallible when it comes to perceiving such a slight difference in timing.

Plus, DNS lookups only come into play for unique site lookups, not sites you’ve visited recently, as these are stored in the DNS resolver cache in your OS. Unless your browsing consists of hitting unique sites the entire time, DNS lookups aren’t coming into play as often as you’d think.

Not to mention that a single Ping test does not give you any indication of actual reliable lookup speeds. You will need to do a study of a week or more during peak and off-peak hours (Ping every 1/2 hour or so) and pick the best average result.

A ping of that amount to CDNS will create lag in multiplayer games at least…

What game are you playing that keeps swapping you to unique server addresses?

Once a URL is resolved, DNS has no further part to play in your connection. The only affect DNS will have (assuming the game server isn’t already cached in your local resolver) is the initial server lookup.

In other words, your computer asks your DNS service what the IP address for WoW realm -whatever, I don’t play Wow- server 2, and your DNS says, oh, it’s ..*.. And that’s it. The delay in reaching your DNS service will not affect your throughput to the server you connect to.

Well as a telecom or BSS technician, we believed that the LOWER the ping value, the fastest connection to the internet you acquired.

since DNS is not a website IP, you do not need to wait for a peak or normal time to test.

well that’s is only my opinion based on my everyday life in telecom industry.

(:WAV) (:WAV) (:WAV)
(:WAV) (:WAV) (:WAV)
(:WAV) (:WAV) (:WAV)

Higher Ping = more travel time delay
Lower Ping = less travel time delay

Of course, but surely has a telecom technician, you must be aware that you can’t confuse DNS lookups with connection speed. How fast a URL is resolved does not affect your overall throughput. Nor does how quickly the URL is resolved give any actual indication of how long it actually takes the server to respond once you have the proper address. Even if your URL is resolved in 47ms, if you are connecting to a server half-way around the world, it’s going to take some time. Time that has nothing to do with your DNS service.

Unless you use your own private DNS service that is hosted on a LAN, Internet congestion will affect your response time for DNS lookups. You are connecting to the service over the Internet after all. :slight_smile:

Of course, but try this test. Using a stopwatch that has tenths of a second accuracy, see how reliable you are at starting and stopping it exactly at a tenth of a second. Pretty quick, isn’t it. :wink:

Can you honestly say that you browsing will be hindered if you have a URL lookup with a service that sports a difference of only a tenth of a second?

What about games based on the peer 2 peer method like Left for Dead, or the new CODs, if and the engine has to negotiate a new host due to poor performance, previous host disconnected, etc.

Again, how often would this be happening? Not enough to really have any impact on lag, I would suspect.

Yes congestion is a part of speed quality but my screenshot here shows my ISP’s DNS is not congested because below 100ms ping is a good sign of DNS quality. that’s why I’am wondering how COMODO DNS performs fast since the latency I got during test is below 300ms? the platform that I used during the test s WiMAX base on a b450 base station that is much faster than the old DSL technology and there is no congestion on a WiMAX network since this kind of broadband uses a sharing of network capacity utilization.

maybe in some country, Comodo DNS performs fast with less latency where COmodo DNS nodes is near to them.

(:WAV) (:WAV) (:WAV)
(:WAV) (:WAV) (:WAV)
(:WAV) (:WAV) (:WAV)

It surely looks like that to me.

200 milliseconds is very noticeable. Most websites have many many urls that points in different directions, when you load a webpage, you are not loading a single web address, there are many addresses being looked up, all the ads that appear, flash video etc. If you load only 5 different hosts you have reached one second RESPONSE-time. the time you see when using ping is not correct, it is lower than the real time, because icmp udp packets are very small and contains little data, like it will do when you request an ip address.

I noticed the comparison in the screenshot above, that was relatively fast in comparison, but my own isp dns response time is even faster. My ISP dns response time is stable at 19 ms, it seldom fluctuates, its very stable. In the 200 ms response time in the example above, my own connection gives me 56 ms stable response time to the comodo dns server.

So 19 ms vs 56 ms in my case.

The traceroute to comodo’s dns servers have 19 hops in my case, the dns server of my isp have only 3 hops.
To each hop, to each subnet you are dependent on, you are more likely to fail the dns request, which means your web browser will display a blank page or a dns error or 404 page not found.

19 hops vs 3 hops, in first case you have alot of dependencies, and sooner or later one of them will be broken. Using as few hops as possible will give a more stable surfing experience.

Also, the longer the route is, the more traffic throughput will be on that network, giving more unstable latencies and more probability that your request will time out, which also results in a blank page.

Considering DNS response time by merely looking at ping statistics is really limited. The more important elements are whether or not your iSP dedicates servers to the task of DNS or whether they’re shared with other customer facing tasks.

Probably one of the most important considerations is the cache used by the ISP DNS, or put another way, how often they cannot service a request without recourse to a higher level.