Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole

Re:Show HN: nextdns.io – A Combination of Cloudflare DNS and... by nextdns on Sunday May 26, 2019 @12:57AM (#20013242)

Could be a routing issue (this things need to be tweaked over time). Can you talk to us via the chat on the website so we can debug?

[ Parent | on HN ]

Re:Show HN: nextdns.io – A Combination of Cloudflare DNS and... by 7ewis on Sunday May 26, 2019 @07:41AM (#20014395)

468ms in the UK.

9ms on Cloudflare, 10ms on Google.

[ Parent | on HN ]

Re:Show HN: nextdns.io – A Combination of Cloudflare DNS and... by jamesog on Sunday May 26, 2019 @02:06PM (#20016395)

There seems to be some routing oddities going on. I'm also in the UK (on AAISP). Sometimes I get ~48ms response, other times 200-300ms.

Looking at mtr I'm occasionally routed to Dallas, Texas. Other times it's correctly routing over my ISP's peering to Vultr.

[ Parent | on HN ]

Re:Show HN: nextdns.io – A Combination of Cloudflare DNS and... by 7ewis on Sunday May 26, 2019 @05:41PM (#20017733)

What command did you run in mtr to see the routing locations?

Or just a normal report, then lookup the IP location?

[ Parent | on HN ]

Re:Show HN: nextdns.io – A Combination of Cloudflare DNS and... by jamesog on Sunday May 26, 2019 @05:54PM (#20017799)

By default mtr will do reverse DNS lookups on all hops. Several of the traces I ran showed the route to nextdns's /24 transiting over NTT and from the DNS name you can figure out where each router is.

[ Parent | on HN ]

Re:Show HN: nextdns.io – A Combination of Cloudflare DNS and... by AtHeartEngineer on Sunday May 26, 2019 @02:32AM (#20013481)

273msec in DC

[ Parent | on HN ]