Live data from Hacker News

DNS over HTTPS

github.com

91–100 of 195 posts

Re: DNS over HTTPS

#91
post #89

Earlier quoted context omitted.

Performant to me implies performing better against the relevant metrics. So faster, maybe, but perhaps smaller and more energy efficient too. If the context of the metrics is already understood then it seems quite a cromulent word.

What's cromulent mean? I looked it up at dictionary.com and couldn't find anything. Or are you making up more words to point out the irony? :)

https://en.oxforddictionaries.com/definition/cromulent

"Acceptable or adequate"

Re: DNS over HTTPS

#92
We prototyped this as an intern project at OpenDNS, too: https://github.com/opendns/OpenResolve

We mostly built it because it sounded cool, but one use case that I though was important was being able to boot these images in different data centers to collect telemetry on DNS differences geographically (eg for hijacking or anycast).

Re: DNS over HTTPS

#93
post #89

Earlier quoted context omitted.

Performant to me implies performing better against the relevant metrics. So faster, maybe, but perhaps smaller and more energy efficient too. If the context of the metrics is already understood then it seems quite a cromulent word.

What's cromulent mean? I looked it up at dictionary.com and couldn't find anything. Or are you making up more words to point out the irony? :)

http://www.dictionary.com/browse/cromulent

Re: DNS over HTTPS

#94
post #87
post #61

Earlier quoted context omitted.

> performant is not considered a real word in English, although I commonly see it used... This is close to being a contradiction in terms. The purpose of words is to communicate, and if a word is being successfully used to communicate -- which clearly it is -- what exactly does it mean to say that isn't "considered a real word"? Also, "Considered" by whom? The dictionary? Dictionaries are descriptivist -- they record…

> (As it happens, "performant" is at the stage where it is starting to pass those thresholds, and is now in the OED [2]) Strictly speaking, I don't believe your [2] is the OED. It's "Oxford Living Dictionaries", which I assume tries to be more current/dynamic, but might be regarded as less authoritative. Interestingly, the word "performant" is in the OED itself, with the earliest citation being from 1809 -- but it is…

Would you prefer the dictionary from Cambridge University Press as a source?

https://dictionary.cambridge.org/dictionary/english/performa...

Re: DNS over HTTPS

#95
post #68

Earlier quoted context omitted.

> All that overhead HTTP adds is wasted for this. When you're in an area where your DNS provider is limited by the state, you won't consider it wasted. But if you're not and you do consider it wasted, don't use it. But saying it doesn't seem to provide any benefit is wrong and just telling people to use a VPN for DNS resolution is also wrong (at least until the ergonomics improve).

It's more a question why a company like Google would pay several engineers who are paid 6-digit sums to build this when they could build for the same or less much more powerful solutions.

[deleted]

Re: DNS over HTTPS

#96

Earlier quoted context omitted.

I don't use it either, and I agree with the poster on that stackexchange link about it sounding like manager/marketing-speak, but when I see it, it makes me pause for a second to think about what really means (perhaps that's the point) --- I had this exchange with a coworker not long ago: CW: ...and this way it'll be more performant too. Me: Performant? As in faster? CW: Yes. Me (to self): Then why didn't you just sa…

Performant to me implies performing better against the relevant metrics. So faster, maybe, but perhaps smaller and more energy efficient too. If the context of the metrics is already understood then it seems quite a cromulent word.

I had just explained the etomology of cromulent to my wife a few days ago - awesome to have an example of its usage in the wild. My hat is off to you, sir.

Re: DNS over HTTPS

#97

> for privacy, performance and security. I understand the privacy and security aspects. But I am wondering - how can DNS over HTTPS be more performant in the case of curl commands? A browser could probably persist the connection to the resolver and issue several requests together, but with a single curl command surely there's the overhead of initiating the first DNS resolve, the HTTPS connection, the second DNS resol…

"Performant" is a word in German. It translates to exact what "perfomant" would mean in english if it were an english word. The funny thing is, google translate, translates the german word "performant" to the english word "performant". https://translate.google.com/?hl=de#de/en/per%C2%ADfor%C2%AD...

We have this word "performant" in Romanian, too, it means something that performs well; it's not limited to IT parlance.

I just checked and the French have it too, I can see how it has slowly made its way into English, through immigration and especially the Internet.

A live language is always changing, resistance is futile. :)

Re: DNS over HTTPS

#98
post #27

I can see how DNS over HTTPS addresses security, but I do not see how it helps with privacy. After resolving the IP address over secure connection HTTPS still sends the host name unencrypted, so one can just eavesdrop on that. And if encrypted DNS becomes widespread, I suspect that various state-imposed firewalls like one Russia will just look for HTTPS connection header to block a particular site.

The industry stance seems to be: SNI not yet being fixed should not be an excuse to preclude work on securing the privacy of DNS requests. SNI Encryption is being discussed: https://www.ietf.org/proceedings/94/slides/slides-94-tls-8.p...

We at DNSFilter are working on client to resolver agents which use DNS over TLS as well as DNSCrypt. We're also looking to create a standard for recursive resolvers like us to communicate securely with authoritative providers (no RFC yet).

Re: DNS over HTTPS

#99

Earlier quoted context omitted.

What dns servers and clients support TLS?

Unbound does it natively, and BIND and the rest use DNSCrypt's shim

While we at DNSFilter are working on support of DNSCrypt, just to add some flavor to your note... it should be mentioned that the original author just abandoned the project, removed the repos from his github user, shut down the website, and it's been setup by a few industry players under a new github org: https://github.com/DNSCrypt

Tough to say what direction the project will take.

I for one welcome other advancements such as Google's efforts.

FWIW, my understanding is if you use Chrome it actually communicates over QUIC

Re: DNS over HTTPS

#100
post #89

Earlier quoted context omitted.

Performant to me implies performing better against the relevant metrics. So faster, maybe, but perhaps smaller and more energy efficient too. If the context of the metrics is already understood then it seems quite a cromulent word.

What's cromulent mean? I looked it up at dictionary.com and couldn't find anything. Or are you making up more words to point out the irony? :)

It's from the Simpsons and that is pretty much exactly the context that it first appeared in! Here's an excerpt from the "Made-up words" article on the simpsons.wikia.com:

When schoolteacher Edna Krabappel hears the Springfield town motto "A noble spirit embiggens the smallest man," she comments she'd never heard of the word embiggens before moving to Springfield. Miss Hoover replies, "I don't know why; it's a perfectly cromulent word".

Post reply on HN