Live data from Hacker News

An interview with Paul Mockapetris, the creator of the DNS

welcometothejungle.com

21–25 of 25 posts

Re: An interview with Paul Mockapetris, the creator of the DNS

#21

Earlier quoted context omitted.

In the past, many DNS servers were configured so you can execute an "ls" to list the subdomains Nowadays most have disabled that option.

Do you have any references for this functionality? I’ve never encountered something like that in the RFCs, or in any server.

Yeah, I think it was for zone transfers. It was pretty fun discovering 'private' hosts :-)

Re: An interview with Paul Mockapetris, the creator of the DNS

#22
post #20
post #18

Earlier quoted context omitted.

It's not about 50% globally. It's like 50% of .SE, which is itself less than 25% as large as .INFO. He's guessing, and he's wrong. That's the point of my comment. I don't care what you do with the observation; he brought it up, and he's way off. (I don't think it's weird that he's way off; I'm not criticizing Mockapetris, just correcting the stat. But your vehemence demands a direct response from me, and I'll provide…

I don’t know what you mean by “vehemence”, but I note that even though you said it “demands a direct reponse”, you didn’t actually answer the question.

I'm sorry, I thought I was clear. No, pointing out that Mockapetris' guess of 50% global adoption of DNSSEC is wrong is not an "argumentum ad populum". It is, as I said, simply an observation that the statistic he is venturing is wrong.

Re: An interview with Paul Mockapetris, the creator of the DNS

#23
post #19

Earlier quoted context omitted.

I wonder if he considered that even under a domain/host/path format, an autocomplete could probably be designed to ignore the domain and search the host. Eg, if you're searching for com/welcometothejungle/en/collections/behindthecode, just start typing "welcometothejungle" and autocomplete will find that substring and return the full URL.

Solution in search of a problem. Whats the issue with having the domain name, an essentially flat map from name to number, going from least general to most general, and a path, representing a file system tree, going from most general down its nodes to the most specific? Is the argument they make up two parts of a url, and thus should behave the same way? Seems a bit superficial.

Yeah if your objective is differentiate between domain and file system path then that’s one way of doing it. That might help with parse-ability, especially if your protocol allows for an optional subdomain which may or not be there, so having a clear separation b/t domain and path might be useful. Hard to know without having been there when these decisions were being made.

Re: An interview with Paul Mockapetris, the creator of the DNS

#24
post #8
post #5

Regarding DNSSEC adoption, for US names: it's less than 2%, just in terms of raw signed domains. It's lower if you're looking at adoption among popular domains.

Source, as of 2020?

Not sure where he's getting his numbers from, but check out: DNSSEC validation, by country from APNIC https://stats.labs.apnic.net/dnssec

Re: An interview with Paul Mockapetris, the creator of the DNS

#25
post #8

Earlier quoted context omitted.

Source, as of 2020?

Not sure where he's getting his numbers from, but check out: DNSSEC validation, by country from APNIC https://stats.labs.apnic.net/dnssec

That's the number of validations, which is effectively a measure of the percentage of people using centralized resolver services that do DNSSEC validation. The figure of merit is the number of signed zones, and, in particular, the percentage of popular zones that are signed (you pick the popularity metric; whatever you choose, the percentage will be extremely low, unless it's "most popular schools and government agencies").
Post reply on HN