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

Show HN: DN$ – an innovative, ad-supported DNS resolver

github.com

Post reply on HN
Print view View original

31–40 of 51 posts

Re: Show HN: DN$ – an innovative, ad-supported DNS resolver

#31

Post by nablags »

yonatan8070 wrote: post #27

Great execution, one of my queries showed this, idk what it means ```dig @35.223.197.204 google.com ;; Warning: ID mismatch: expected ID 37255, got 53558``` Great project, I found out about a course that'll help me make 100,000 USD a month!

An ID mismatch occurs when the ID on your DNS query differs from the ID on your DNS response. Queries & Responses should share the same ID - either this has been done intentionally or it's a sign that something is buggy with the resolver.

This sounds like a serious, security vulnerability. We'll investigate it in 3-5 years

Re: Show HN: DN$ – an innovative, ad-supported DNS resolver

#32

Post by yonatan8070 »

nablags wrote: post #31
yonatan8070 wrote: post #27

Great execution, one of my queries showed this, idk what it means ```dig @35.223.197.204 google.com ;; Warning: ID mismatch: expected ID 37255, got 53558``` Great project, I found out about a course that'll help me make 100,000 USD a month!

An ID mismatch occurs when the ID on your DNS query differs from the ID on your DNS response. Queries & Responses should share the same ID - either this has been done intentionally or it's a sign that something is buggy with the resolver. This sounds like a serious, security vulnerability. We'll investigate it in 3-5 years

Given that the server is written in Rust, it is perfect and has no bugs. This must be a cosmic ray that hit a router on the way

Re: Show HN: DN$ – an innovative, ad-supported DNS resolver

#34

Post by bee_rider »

naikrovek wrote: post #29

I hate April Fool’s day so much. No, this didn’t trick me. Lying and pranking are both bad things to do, and they’re bad on 1 April, too. If you find this kind of thing fun, we can’t be friends and I will forever look down at you. It’s my problem, I know, I just can’t condone pranking or deception for any reason.

Harmless pranks are good. They are our way of vaccinating people against real lies.

Re: Show HN: DN$ – an innovative, ad-supported DNS resolver

#35

Post by chuckadams »

PreInternet01 wrote: post #4

> DN$ only supports DNSSEC for customers in the ENTERPRISE tier OK, so how much do I pay you to change that message to "DNSSEC is pointless and you should feel bad for making this request"?

Why change the message instead of adding another? Any smart company should be able to offer support contracts for pointless things.

Re: Show HN: DN$ – an innovative, ad-supported DNS resolver

#36

Post by proactivesvcs »

Here's me, a Uniformly Dopey Peasant.

  nmap -sV -p 53 35.223.197.204
  Starting Nmap 7.94SVN ( https://nmap.org ) at 2024-04-01 20:16 BST
  Nmap scan report for 204.197.223.35.bc.googleusercontent.com (35.223.197.204)
  Host is up (0.11s latency).

  PORT   STATE SERVICE VERSION
  53/tcp open  domain?
  1 service unrecognized despite returning data. If you know the service/version, please submit the
  following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service :
  SF-Port53-TCP:V=7.94SVN%I=7%D=4/1%Time=660B081A%P=x86_64-pc-linux-gnu%r(DN
  SF:SVersionBindReqTCP,4F,"\0M\0\x06\x81\x05\0\x01\0\x01\0\0\0\0\x07version
  SF:\x04bind\0\0\x10\0\x03\xc0\x0c\0\x10\0\x01\0\0\0d\0#\"TCP\x20is\x20for\
  SF:x20enterprise\x20clients\x20only")%r(DNSStatusRequestTCP,3D,"\0;\0\0\x9
  SF:0\x05\0\0\0\x01\0\0\0\0\xc0\x0c\0\x10\0\x01\0\0\0d\0#\"TCP\x20is\x20for
  SF:\x20enterprise\x20clients\x20only");

Re: Show HN: DN$ – an innovative, ad-supported DNS resolver

#37

Post by KomoD »

yonatan8070 wrote: post #32
nablags wrote: post #31

Earlier quoted context omitted.

An ID mismatch occurs when the ID on your DNS query differs from the ID on your DNS response. Queries & Responses should share the same ID - either this has been done intentionally or it's a sign that something is buggy with the resolver. This sounds like a serious, security vulnerability. We'll investigate it in 3-5 years

Given that the server is written in Rust, it is perfect and has no bugs. This must be a cosmic ray that hit a router on the way

It's a feature!
Post reply on HN