Live data from Hacker News

Mess with DNS

jvns.ca

31–40 of 94 posts

Re: Mess with DNS

#31

Earlier quoted context omitted.

hypothetically, what happens if a domain is catalogued by malicious? Also who catalogues it? If you haven't bought the domain from Google, the only thing that Google can do is not show the domain on google search results. Did I miss anything?

> If you haven't bought the domain from Google, the only thing that Google can do is not show the domain on google search results. Did I miss anything? I would imagine they might also show warnings in Chrome.

Pretty much all major browsers check against Google's safe browsing list so it's pretty much a death sentence to be on it.

Re: Mess with DNS

#33
post #32

Quoted post unavailable.

The tone of your comment is pretty inappropriate. The whole point of this is to help people learn about DNS, including the author, who happens to be one of the most humble and helpful persons on the internet.

No volume of books can be adequately substituted for doing something, which this project enables handily.

I'm sure you'll be down voted to oblivion but maybe consider a more constructive approach, like opening a PR and helping the authors out.

Re: Mess with DNS

#34
post #32

Quoted post unavailable.

I don't really agree with the tone of your comment, and why would you cite a section of the article where the author was talking about a front-end testing framework?

Re: Mess with DNS

#35
post #32

Quoted post unavailable.

Someone is missing knowledge, admits it, and this somehow inflames you? They created a free tool. Nowhere do they claim that this is a comprehensive replacement of a full O'Reilly book.

Re: Mess with DNS

#37
post #32

Quoted post unavailable.

Some of my fondest memories were learning programming and then infrastructure engineering in bits and pieces while so many “veterans” at the time pissed and moaned about how the One True Way to learn was reading O’Reilly books.

A decade into my career, I’m pretty sure I out-earn nearly all of them despite them having a solid decade on me. Of course, income is a fallible indicator, and to the extent that it’s accurate, I don’t think the difference is “reading books vs Googling” but rather (if I had to guess) some handicap that correlates with bitching about how other people learn on the Internet.

Re: Mess with DNS

#38
post #14

On the security aspect, I wonder how is this site affected services that do domain ownership verification [1] where they assume that only a person who owns the domain can edit dns records. I think letsencrpt ACME protocol [2] does it for SSL certs too. This site does create a subdomain for every user, so may be these issues don't apply. [1] https://support.google.com/a/answer/183895?hl=en [2] https://letsencrypt.org/…

I would think it would fall on the zone operator to properly configure a CAA record to restrict issuance by an unauthorized CA.

Re: Mess with DNS

#39
post #14

On the security aspect, I wonder how is this site affected services that do domain ownership verification [1] where they assume that only a person who owns the domain can edit dns records. I think letsencrpt ACME protocol [2] does it for SSL certs too. This site does create a subdomain for every user, so may be these issues don't apply. [1] https://support.google.com/a/answer/183895?hl=en [2] https://letsencrypt.org/…

There's also the public suffix list: https://publicsuffix.org/list/

It's probably a good idea for the author to add this project to the list.

Re: Mess with DNS

#40
post #32

Quoted post unavailable.

life is too short for that.

it is incredible valuable to have a basic understanding of many things. Julia just built a tool which will help me learn the basics of DNS in 20min.

Post reply on HN