Hacker News Reader

Comment by dbg31415 | Hacker News Reader

dig +noall +stats @1.0.0.1 news.ycombinator.com; dig +noall +stats @1.1.1.1 news.ycombinator.com; dig +noall +stats @208.67.220.220 news.ycombinator.com; dig +noall +stats @208.67.222.222 news.ycombinator.com; dig +noall +stats @8.8.4.4 news.ycombinator.com; dig +noall +stats @8.8.8.8 news.ycombinator.com

Fixed? =P

I removed some of the records form the article after reading some of the comments here. Cloudflare, Google, and OpenDNS only.

Kind of cool, I switched it up and ran it against 10 sites I frequent... was pretty impressed to see how well OpenDNS was doing.

View on HN

That tests ICMP echo requests not name resolution.

That is what original test was testing.

What? It says

>Our test was very simple and we performed 70 DNS lookups

That's not ICMP.

Well, the article says so, but they actually measured icmp response. All major domains are in DNS cache anyway. If you look at Yandex result you see it performed very poorly. Why does it resolve popular domains so slow? The reason is it has one server and it is located in Moscow.

So i would say icmp is good proxy to actual performance.

It would be a measure of ping + cache latency. That's still different than just ping.

And is your point that the tested sites aren't popular in Russia?

>for different popular domains (google, facebook, twitter, gmail, etc)

google.com facebook.com and twitter.com are all in the top 50 sites in Russia[1]. And gmail.com is number 6000 globally[2], so it's unpopular everywhere, not just Russia. Popular sites in Russia tend to be popular elsewhere, and vice versa.

[1] https://www.similarweb.com/top-websites/russian-federation

[2] https://www.alexa.com/siteinfo/gmail.com

all these sites are popular in Russia, so we can presume cache latency is a constant on all tested servers. What left is a ping, packet response time.

This whole subtree of comments is really messy with all the editing several of you people did.

It would be better to just delete this whole subtree.

You should be doing `dig @1.1.1.1 news.ycombinator.com`

That resolves "news.ycombinator.com" and "1.1.1.1" with your system resolver.

You're looking for "dig @1.1.1.1 news.ycombinator.com" which will resolve "news.ycombinator.com" using "1.1.1.1".

Thanks, I wrote that from memory. I'll update my comment.

Sorry, I've downvoted you (even though you're not being offensive in any way) because your incorrect command will confuse a bunch of people.

EDIT: fixed, so I've undowned

Reply on news.ycombinator.com