Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chromium's Impact on Root DNS Traffic

blog.apnic.net

Post reply on HN
Print view View original

91–100 of 221 posts

Re: Chromium's Impact on Root DNS Traffic

#91

Post by teddyh »

stefan_ wrote: post #68
pilif wrote: post #64

Earlier quoted context omitted.

how would they maintain the root servers and correct issues without shell access or tcpdump? Make blind guesses and restart the server until the problem goes away (it won't)? No matter how high-profile the environment, eventually, the rubber will hit the road and some human will be in a privileged position to be able to fix a problem. That is true for every single service out there. Yes. Including Gmail. Including AW…

Why is a server with a problem still part of the root zone? And no, this is absolutely not the case for serious operators. Access to production systems is highly regulated.

OK, so say you remove it, and the problem goes away. Now what do you do? How do you find out what was actually going on?

Re: Chromium's Impact on Root DNS Traffic

#93

Post by johncolanduoni »

1vuio0pswjnm7 wrote: post #49

Why does Chrome (Google) need to know whether DNS is being intercepted? What actions does Google take based on the answer? Note that under this crude test of sending queries for unregistered domains, a user who administers their own DNS could be indistingushiable from "DNS interception" by an ISP or other third party. I administer my own DNS. I do not use third party DNS. These random queries would just hit my own DN…

Since these are root queries, wouldn’t your DNS server need to hit the root servers to ensure the TLDs don’t exist? Also your own DNS won’t be detected as DNS interception unless you replace NXDOMAINs with fake responses.

Re: Chromium's Impact on Root DNS Traffic

#94

Post by gsich »

elric wrote: post #46
g2347890 wrote: post #36

Earlier quoted context omitted.

all technically deprived people I have seen, use none of the above, the first thing they do is open google (most have it nowadays in defult tab page) and they type the URLs given to them there, no one knows about address/search bar, and if some know, they expect it to work like the google search box Update: I hide some site of mine from google, I do not care about SE traffic and block any crawler, and I have noticed…

Isn't that just a matter of educating users? Users, contrary to popular belief, are not stupid. Everyone starts off knowing nothing at all, but we can teach them what an address is and we can teach them how to search for things.

I think the ratio of people who know stuff stays roughly the same.

Re: Chromium's Impact on Root DNS Traffic

#95

Post by johncolanduoni »

corty wrote: post #50
thayne wrote: post #25

Earlier quoted context omitted.

Google could, you know, use their own DNS servers for this...

They could just use DNSSEC...

DNSSEC has to be supported by your ISP’s DNS server, which they won’t if they’re trying to intercept your queries.

Re: Chromium's Impact on Root DNS Traffic

#96

Post by teddyh »

londons_explore wrote: post #78
encom wrote: post #67

Earlier quoted context omitted.

This comment, and another one mentioning DNSSEC has been downvoted. Please explain why you hate DNSSEC instead of downvoting things you disagree with.

Browser vendors seem to have shelved all work on DNSSEC for reasons they haven't publically stated. It had such promises to be able to reduce trust in CA's by pinning HTTPS certificates to DNS responses, so was exactly what browsers would have wanted, yet still all work stopped around 2015 or so. To me, it's as if DNSSEC has some critical and unfixable security vulnerability, and people who make these decisions decid…

That blog post is five years old, and most of the things it lists are now moot.

Re: Chromium's Impact on Root DNS Traffic

#97

Post by AndyMcConachie »

jiggawatts wrote: post #5

I'm curious to know how much data the root namespace servers put out in terms of gbps, but this doesn't seem to be public information.

You can look at the RSSAC002 data as well. It doesn't count bandwidth, but it counts lots of other stuff.

https://github.com/rssac-caucus/RSSAC002-data

You can also click on the "RSSAC" button on root-servers.org to get the YAML straight from the root server operators themselves.

Most of the root server operators have anycast instances deployed in organizations that host the servers for them. So there's not an easy way to measure bandwidth utilization because many root server anycast instances are hosted in organizations that may not, or could not, report that bandwidth utilization. Look at the map on root-servers.org to see how dispersed around the world these things are.

Re: Chromium's Impact on Root DNS Traffic

#99

Post by tylercrompton »

mehrdadn wrote: post #88
brown9-2 wrote: post #86

Earlier quoted context omitted.

You can prefix your searches in the omnibox with “?” and they won’t be treated as possible short local network names

Ctrl+K for Windows users looking for a shortcut key.

That works on multiple platforms! I'm able to do that on Arch.
Post reply on HN