[terragon]

I tried using it. I'm in India, and while Cloudflare and Google DNS consistently resolve in 60-70ms, nextdns takes between 400-700ms for the first resolution and consistently 250ms for the same query repeated (I presume it caches the results?)

Should I assume you've gotten a huge spike in traffic because of this HN post? If yes, I don't mind trying again in a few days, but unless things improve, I wouldn't be able to use it despite loving it in concept (the UI of your implementation is great too). I don't want to discourage you folks, since you've done a great job with the rest of it.

Thanks for your efforts.

[LogicX]

Disclaimer: I run a competing service.

India is difficult. I run our anycast network and we have coverage in India but I look forward to improved routing there in the future with additional transit providers.

It seems nextdns is announcing exclusively with Vultr: https://bgp.he.net/net/5.182.208.0/24

Which is not in India: https://www.vultr.com/locations/

[nextdns]

It's not the spike, it's probably a combination of:

- a routing imperfection (this things need to be tweaked over time).

- the fact that we didn't deploy our PoP in India yet (coming this month).

Can you talk to us on the chat if you have some time? It would help to do some debugging.

[Terretta]

Great idea for service, but it has to be lightning fast to be in the middle of thousands of requests a minute as someone is surfing the web without making the web feel sluggish.

In NYC on the largest metro ISP. Earlier in the day, was getting 25-43 msec to the typical major DNS providers (1.1.1.1, 4.4.4.4, 8.8.8.8, 9.9.9.9, as well as AdGuard), and usually 71 - 73 msec to you.

After a while, started getting as slow as 280 msec to you.

Last hour or so, mostly just getting timeouts to you, making the web, as well as apps, unusable.

Had to revert.

AdGuard DNS:

    dig @176.103.130.130 news.ycombinator.com
    
    ; <<>> DiG 9.10.6 <<>> @176.103.130.130 news.ycombinator.com
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6879
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;news.ycombinator.com.  IN A
    
    ;; ANSWER SECTION:
    news.ycombinator.com. 56 IN A 209.216.230.240
    
    ;; Query time: 29 msec
    ;; SERVER: 176.103.130.130#53(176.103.130.130)
    ;; WHEN: Sun May 26 15:32:11 EDT 2019
    ;; MSG SIZE  rcvd: 85

nextdns.io

    dig @5.182.208.100 news.ycombinator.com
    
    ; <<>> DiG 9.10.6 <<>> @5.182.208.100 news.ycombinator.com
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14810
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;news.ycombinator.com.  IN A
    
    ;; ANSWER SECTION:
    news.ycombinator.com. 0 IN A 209.216.230.240
    
    ;; Query time: 282 msec
    ;; SERVER: 5.182.208.100#53(5.182.208.100)
    ;; WHEN: Sun May 26 15:32:17 EDT 2019
    ;; MSG SIZE  rcvd: 85

[miyuru]

Try to do MTR and check for the routing.

I am from Sri Lanka and I get following over IPv6 using dig,

80-120ms for Nextdns (92ms avg ping)

75-140ms for Google (61ms avg ping)

70-90ms for Cloudflare (75ms avg ping)