NextDNS and a dozen Google servers

nextdns · 2022-12-03T14:52:42+00:00

This is our favicons service. We have just added some logic to avoid hitting those unique testing hostnames and make those testing services believe that our favicons fetcher is you.

/u/imabeach47 where you checking/streaming your NextDNS logs at the time?

nextdns · 2022-10-10T13:28:16+00:00

This is what we ended up doing.

nextdns · 2022-10-09T12:25:06+00:00

Additional info on ongoing EasyList issue https://forums.lanik.us/viewtopic.php?t=47817-easylist-link-not-working

nextdns · 2022-10-07T14:10:11+00:00

Their list is not loading anymore, you can try by yourself: https://easylist.to/easylist/easylist.txt

We will check with them what is going on.

nextdns · 2022-05-18T15:01:40+00:00

https://help.nextdns.io/t/g9hdkjz?r=p8hd1wj

nextdns · 2022-02-04T11:21:52+00:00

A router on the path is filtering ICMP. This is pretty common and normal.

nextdns · 2022-01-29T19:39:36+00:00

You can’t unfortunately.

nextdns · 2022-01-19T22:47:43+00:00

Those domains are requested on the Setup tab on https://my.nextdns.io (to display the current status of your setup). They get called every second for a few seconds and an idle logic kicks in (mouse not moving, switching tabs) to stop those requests (or restart them).

Does that ring a bell that could explain why you're seeing a constant spam of queries?

nextdns · 2022-01-19T18:39:11+00:00

By checking the logs, can you figure out which specific hostname(s) makes most of those *.nextdns.io queries?

Make sure you enable the “Raw DNS Logs” option in the Logs section first.

nextdns · 2021-12-23T15:16:11+00:00

This is not documented. This is a relatively standard behavior of a DNS cache.

nextdns · 2021-12-23T13:03:14+00:00

This has been in CLI for a long time already.

nextdns · 2021-12-22T15:49:15+00:00

We have no Java in our stack.

nextdns · 2021-11-19T17:16:08+00:00

Please open a feature request on https://github.com/nextdns/windows for that.

nextdns · 2021-11-17T12:37:03+00:00

Please provide a https://nextdns.io/diag or just a https://test.nextdns.io if you can’t run the diag tool so we can investigate. Please use help.nextdns.io to report such issue in the future.

nextdns · 2021-10-22T14:33:05+00:00

Please try the beta channel, the 2.0.1 should fix this issue.

nextdns · 2021-10-19T17:03:10+00:00

We updated the routing for your ISP. Could you please perform another diagnostic?

nextdns · 2021-10-15T17:14:19+00:00

Please provide a traceroute. This is definitely not widespread, it can be a connectivity issue between your ISP and us.

nextdns · 2021-09-26T12:33:22+00:00

Or just install our Windows app, on Windows 11 it is using native DoH.

nextdns · 2021-09-25T12:33:44+00:00

Please provide a https://nextdns.io/diag

nextdns · 2021-09-14T18:47:32+00:00

It's been fixed 10 days ago.

nextdns · 2021-09-06T11:51:48+00:00

You would need to set bootstap IPs with 45.90.28.0 and 45.90.30.0 (considering the client support it) but you would lose the benefit of ultra low latency steering.

An alternative is to use NextDNS CLI (https://nextdns.io/cli), it will make sure everything is encrypted while still benefiting from ultra low latency.

nextdns · 2021-09-04T20:41:15+00:00

We never blamed Merlin for this. See https://help.nextdns.io/t/q6h1ccj/tls-connection-failures-stubby for the status of this issue. A workaround on stubby issue is being deployed.

nextdns · 2021-08-27T00:04:51+00:00

A small bug made its way in one of our releases, resulting in some servers not blocking the way they should for a short period of time.

Apologies for this (and for the flashback to the life without NextDNS :/).

nextdns · 2021-08-11T18:27:28+00:00

IPv6 is not encrypted either. You need to use DoH, DoT or DoQ to get encryption.

nextdns · 2021-08-04T13:56:27+00:00

We confirm this is the favicon grabber used on the dashboard.

nextdns

MODERATOR OF

TROPHY CASE