Matthew Zipkin

This seems to not be a problem any more ...? ``` --> dig @127.0.0.1 -p 25350 violation ; DiG 9.18.9 @127.0.0.1 -p 25350 violation ; (1 server found) ;; global...

This has come up again in a branch where hnsd can discover peers and open more connections: https://github.com/handshake-org/hnsd/pull/38#issuecomment-681883190

Got a stack trace of this: ``` peer 714 (64.227.15.172:12038): sending verack [25/1965] peer 714 (64.227.15.172:12038): sending sendheaders peer 714 (64.227.15.172:12038): sending getaddr peer 714 (64.227.15.172:12038): sending getheaders corrupted double-linked...

I was able to resolve `welcome.nb` with this patch (without the `www.` which doesn't exist) but it highlights a big problem in this design, names are getting redirected wrong. In...

does your router allow any recursive dns traffic? Because even if the root resolution is done internally, the recursive resolver will still need to make requests to port 53 on...

> Wouldn't this mean that hns resolution itself would not work on a hostile network that tampers with traffic on port 53? Correct, in my hotel last week I experienced...

So, unfortunately I think I need cut bait on this one for now and come back to it later, it may require a much bigger refactor or actually patching up...

Funny, that is a node I run and also I've seen the same error when connecting to that same node. The node has 247 inbound connections and great uptime, I'm...

> Do you mean multiplied by `* 1e6`? Yes I either meant `* 1e6` OR `* (10 ** 6)` sorry... exponent: https://github.com/handshake-org/hs-client/blob/533b1403f381c086fc364545d88410fc38e8c0f4/bin/hsw-cli#L7 base: https://github.com/bcoin-org/bcfg/blob/05122154b35baa82cd01dc9478ebee7346386ba1/lib/config.js#L1190 Looks like some of these parameter...

Probably part of the hard coded root zone issue: https://github.com/handshake-org/hnsd/issues/91