NextDNS app possible latency issues

[Kcajminer2312]

Continuing the discussion from DOH with NextDNS app:

@lleachii

better readership of your [new] issue.

except this the same issue

and wherever closed this has really annoyed me

I only tested for a few seconds, I might moved the whole network over the the router DNS again and see if there's any change, we could be changing ISP for no reason

@lleachii

I asked you to test 1 website - only because of your latency comment. If you use IP successfully, you can eliminate DOH as the cause.

yes, I was annoyed

I tested an IP address and couldn't tell the difference, maybe 1ms difference on a ping test, thats probably not even the correct test

there might not be an issue at all here, but it does feel slower

@Kcajminer2312

same results, sorry for bringing this up here

except I believe these results are expected 13ms to google.com is fine

maybe its not the ISP after all, and the latency seems consistent

[Kcajminer2312]

solution: stop blaming our ISP and blame openwrt instead

DNS caching at the router really seems to make a difference

thats the whole reason we moved to the nextdns app

I will just do it as not encrypted DNS from the router or not use nextdns at all

[topsbr]

I had a lot of problems with NextDNS. I was always opening support tickets with them and they never responded. When my subscription ended, I migrated to AdguardHome, pointing to Cloudflare's DNS. The problems stopped.

[Kcajminer2312]

@topsbr

I was always opening support tickets with them and they never responded.

I attempted to email with no response

some devices say there connected to London(zepto-lon-1), some do not (vultr-ams-1)

I might go back to pi-hole, but the co-founder had a massive argument with me

even the ISP DNS server seems faster then NextDNS, or maybe thats because the router is caching, if I used pi-hole again it would be properly cached

is a 3 second loading delay normal for a FTTP connection, we have decided to stay with our current ISP but I think this delay is higher than it was before

[lleachii]

@Kcajminer2312

except this the same issue

@Kcajminer2312

I will be attempting to use the nextdns app for per client DNS requests tracking, where every client needs to send its hostname with the DOH endpoint

the only problem I see here is the routing as openwrt is not the main router

OK, you eliminated the OpenWrt.

@Kcajminer2312

I changed my DNS to 192.168.1.1, which bypass the openwrt device

Can you explain how this is the same issue if you've eliminated the OpenWrt device thru bypassing it (and I assume NextDNS)?

(I understand you see different configuration problems on the same device as being "related", but clearly a more specific description of each problem is required. Conflating issues together causes confusion and misunderstanding of the purpose of changes, mistaking changes as resoultion to other issues, etc.)

@Kcajminer2312

is a 3 second loading delay normal for a FTTP connection

Loading delay when doing what?

Where do you live (otherwise, how can we answer that)?

@Kcajminer2312

thats probably not even the correct test

Test your connection without NextDNS (if that's what you identified as possibly causing the issue), pretty simple.

[Kcajminer2312]

@lleachii

@Kcajminer2312

I will be attempting to use the nextdns app for per client DNS requests tracking, where every client needs to send its hostname with the DOH endpoint

the only problem I see here is the routing as openwrt is not the main router

OK, you eliminated the OpenWrt.

that was the old thread first post

I was using the openwrt device at that time

@lleachii

Can you explain how this is the same issue if you've eliminated the OpenWrt device thru bypassing it (and I assume NextDNS)?

I bypassed it to test latency, and it seems to be slightly better

I do think we have a minor connection problem, but that's for the ISP to fix

@lleachii

Loading delay when doing what?

webpage load times, web app load times

@lleachii

Where do you live (otherwise, how can we answer that)?

connection ping is 8ms

"Measure-Command { nslookup google.com 192.168.1.1}" says 52ms

"Measure-Command { nslookup google.com XX.XX.XX.XXX}" nextdns ip says 265ms

that's from my PC, so I NextDNS does not seem to be the issue, openwrt could have been add extra though

@lleachii

Test your connection without NextDNS (if that's what you identified as possibly causing the issue), pretty simple.

I am using ISP DNS and maybe for good, its wasn't much faster the first few times, now its fasters so the router is caching DNS

All this setup has done is cause connectivity problems for the whole network

Its made us change provider with a one touch switch, which can hopefully be canceled as its not happened yet

so thread closed, I am no longer going to be using openwrt

I could pass the router DNS to NextDNS or just use local adblock

[lleachii]

@Kcajminer2312

nslookup google.com 192.168.1.1}" says 52ms

@Kcajminer2312

nextdns ip says 265ms

that's from my PC, so I NextDNS does not seem to be the issue,

NextDNS is not the issue?

Wow, OK - I interpreted your results very differently.

@Kcajminer2312

so thread closed, I am no longer going to be using openwrt

[Kcajminer2312]

@lleachii

NextDNS is not the issue?

Wow, OK - I interpreted your results very differently.

that 52ms is quite high really, I don't think Measure-Command is getting the correct time, I think I will try again on linux with dig

"Query time: 11 msec" to 192.168.1.1 which is actually going to NextDNS now

and exactly the same to Cloudflare 1.1.1.1

[lleachii]

@Kcajminer2312

that 52ms is quite high really

@Kcajminer2312

nextdns ip says 265ms

And 265ms is even higher. Anyway, as I said, I'm clearly misinterpreting your posted results (or the 192.168.1.1 device was reconfigured to perform a different task since your last description).

@Kcajminer2312

Query time: 11 msec" to 192.168.1.1 which is actually going to NextDNS now

Then what was 52ms?

Yep, something changed. Again, it's difficult when you say reference a previous thread that supposedly has all the information, but then you mention changes later in the discussion.

@Kcajminer2312

Measure-Command

Interesting choice to test.

[Kcajminer2312]

@lleachii

And 265ms is even higher. Anyway, as I said, I'm clearly misinterpreting your posted results

I am misinterpreting my own results, that's a poor response time, but I think that was a fault of windows powershell

@lleachii

Then what was 52ms?

the 52ms was windows powershell, the 11ms is dig in Debian WSL

@lleachii

Yep, something changed. Again,

nothing has changed, just the software used for testing

@lleachii

Yep, something changed. Again, it's difficult when you say reference a previous thread that supposedly has all the information, but then you mention changes later in the discussion.

Nothing has changed, only the fact openwrt is unplugged and the router DHCP being used

I may plug it back in at a later date

@lleachii

Interesting choice to test.

Its what Bing copilot told me to use to measure nslookup times in windows

[lleachii]

@Kcajminer2312

Nothing has changed, only the fact openwrt is unplugged

Yea, clearly I'm missing your intended goal in this testing. And if the OpenWrt isn't connected, I don't understand the posts in this forum and the comments about planning to stop using OpenWrt.

@Kcajminer2312

nextdns ip says 265ms

Was this test result with the OpenWrt?

(In other words - I'm trying to understand how a unplugged OpenWrt is involved in this issue, how these tests results offer clarity, and how the information in the previous thread is helpful, given you've unplugged the OpenWrt.)

[Kcajminer2312]

I will be using OpenWrt again

All I really want from this now is

Can OpenWrt cache DNS queries and send to NextDNS at the same time

client uses cache for speed, but also forwards to NextDNS

is that possible?

I don't believe there's any cache at the moment

@lleachii

Yea, clearly I'm missing your intended goal in this testing

I was testing with and without OpenWrt and actually there's only minor difference

@lleachii

Was this test result with the OpenWrt?

with my PC and we know that that result was messed up

@lleachii

I'm trying to understand how a unplugged OpenWrt is involved in this issue, how these tests results offer clarity

I though it was adding too much latency

@lleachii

you've unplugged the OpenWrt

I will be connecting it again later today

[lleachii]

@Kcajminer2312

with my PC and we know that that result was messed up

Yes, I know it was with a PC - but with what router, configuration, etc. (please provide relevant details)?

As we discussed in PM, this is an OpenWrt forum, so, I was just seeking clarification. If not OpenWrt, please let us know to end any confusion.

@Kcajminer2312

I though it was adding too much latency

If it's without the OpenWrt, you can safety surmise that the OpenWrt can't be causing the issue.

@Kcajminer2312

I will be connecting it again later today

We discussed in PM that it's expected that a user is employing an OpenWrt device if seeking advise in the OpenWrt forum. Feel free to provide the configurations and description of the setup once reconnected (please don't reference an old thread).

Also, since we know the OpenWrt was unplugged, remember to describe the actual issue [with an OpenWrt device] that you'd like assistance in troubleshooting.

Edit:

Also, since it's clear this thread blames and discusses an unplugged OpenWrt which is technically impossible, and since there's no OpenWrt in this setup, let's make a new thread for any new isssue that you experience.

(Additionally, since the OpenWrt is unplugged, we know your NextDNS resolution latency issue is unrelated to OpenWrt. No need to seek assistance here, as you identified it as unrelated.)

Edit 2:

Especially since you mentioned in PM that your goal was to ask the OpenWrt forum about non OpenWrt issues.

[Kcajminer2312]

an engineer from our ISP is coming out, so it was definitely a problem with the ONT

Sorry for wasting your time

@lleachii

Yes, I know it was with a PC - but with what router, configuration, etc. (please provide relevant details)?

I used OpenWrt and the router when testing, I passed a server IP to dig/nslookup

@lleachii

As we discussed in PM, this is an OpenWrt forum, so, I was just seeking clarification. If not OpenWrt, please let us know to end any confusion.

I will only post openwrt from now on, I did know that, sorry

@lleachii

If it's without the OpenWrt, you can safety surmise that the OpenWrt can't be causing the issue.

yes, that's why I am using it again

its maybe 1-2ms more latency, its nothing

@lleachii

We discussed in PM that it's expected that a user is employing an OpenWrt device if seeking advise in the OpenWrt forum

I suppose I don't need to reply to everything, when I have already said above

@lleachii

once reconnected (please don't reference an old thread).

the explains how we got to this point though, I would say that's important

but my explanations were not clear enough, so I do understand

@lleachii

Also, since we know the OpenWrt was unplugged, remember to describe the actual issue [with an OpenWrt device] that you'd like assistance in troubleshooting.

my only thing now, is DNS caching possible?

while still passing to NextDNS

client uses cache, queries is forwarded and cache is updated, is that possible?

@lleachii

Also, since it's clear this thread blames and discusses an unplugged OpenWrt which is technically impossible

its not unplugged now, I have been without it for 24 hours, maybe 48 hours

its back as NextDNS is hard to understand when everything is one device, it makes it harder to whitelist domains, as you can not see the doamins you need

@lleachii

and since there's no OpenWrt in this setup, let's make a new thread for any new isssue that you experience.

I will be repeating myself agin

@lleachii

let's make a new thread for any new isssue that you experience.

another new thread, this one is still accurate

There is a network issue outside of our control, but I would still like faster DNS if possible

as thats 16-20ms down to 1-2ms with a local cache

@lleachii

(Additionally, since the OpenWrt is unplugged, we know your NextDNS resolution latency issue is unrelated to OpenWrt. No need to seek assistance here, as you identified it as unrelated.)

engineer visit like mentioned above

@lleachii

Especially since you mentioned in PM that your goal was to ask the OpenWrt forum about non OpenWrt issues.

I was asking for latency advise as we was halfway though leaving our ISP and they was not bothered about issues

Now we are back with them, they are back to trying to fix the issues

again, I am sorry for talking about non-openwrt devices

it will not happen again, I do not want to be banned again

summary:

an engineer from our ISP is coming out

Is DNS cache possible, like I said above?

[lleachii]

@Kcajminer2312

the explains how we got to this point though, I would say that's important

but my explanations were not clear enough, so I do understand

Your explanations were 100% clear - the problem is (as discussed in the PM) your expectation that people on the OpenWrt forum were here to assist with non OpenWrt issues.

@Kcajminer2312

another new thread, this one is still accurate

Again:

@lleachii

Also, since it's clear this thread blames and discusses an unplugged OpenWrt which is technically impossible, and since there's no OpenWrt in this setup, let's make a new thread for any new isssue that you experience.

This thread is not accurate, since this thread is about a setup that doesn't even include an OpenWrt device.

@Kcajminer2312

an engineer from our ISP is coming out

Is DNS cache possible, like I said above?

Again, as above, please make a new thread for a new issue.

---

@slh, @psherman , can we close this thread?

[lleachii]

@Kcajminer2312

DNS caching at the router really seems to make a difference

@Kcajminer2312

even the ISP DNS server seems faster then NextDNS, or maybe thats because the router is caching, if I used pi-hole again it would be properly cached

@Kcajminer2312

now its fasters so the router is caching DNS

@Kcajminer2312

client uses cache for speed, but also forwards to NextDNS

is that possible?

I don't believe there's any cache at the moment

@Kcajminer2312

my only thing now, is DNS caching possible?

@Kcajminer2312

Is DNS cache possible, like I said above?

Just to be clear - I saw this information, but each time (and throughout this thread) you were discussing a setup with a non-OpenWrt device. As I noted in PM:

If you have an inquiry about re-enabling DNS cache that was probably disabled by your numerous "minor" or "useless" configuration edits never discussed or undertaken previously for a different reason (i.e., because you setup direct DoH instance to each device to NextDNS when using the https-dns-proxy package), feel free to create a new thread

[dave14305]

@Kcajminer2312

Can OpenWrt cache DNS queries and send to NextDNS at the same time

In theory, there is a cache-size option in nextdns CLI. Try it without adding "sudo" to the command.

Cache Configuration

[psherman]

Based on the following comments from the OP:

@Kcajminer2312

so thread closed, I am no longer going to be using openwrt

@Kcajminer2312

I am misinterpreting my own results, that's a poor response time, but I think that was a fault of windows powershell

@Kcajminer2312

I was testing with and without OpenWrt and actually there's only minor difference

@Kcajminer2312

an engineer from our ISP is coming out, so it was definitely a problem with the ONT

@Kcajminer2312

yes, that's why I am using it again

its maybe 1-2ms more latency, its nothing

... this thread can now be closed.