Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AdGuard unflitered public DNS 10 times slower than filtered public DNS #888

Open
pictosun opened this issue Jan 30, 2025 · 3 comments
Open
Labels
bug Something isn't working

Comments

@pictosun
Copy link

pictosun commented Jan 30, 2025

Platform

Other

Protocol

DNS-over-HTTPS

Do you use AdGuard app?

No I don't

Your configuration

AdGuard Home with Upstream Servers

Traceroute to AdGuard DNS

./.

Issue Details

Using AGH and AdGuard Upstream Servers.

Average upstream response time from the servers is totally different.

AGH seats within EU.

Expected Behavior

avg response time should be nearly the same and not ten times as much.

Actual Behavior

response time of unfiltered is ten times as much as filtered DNS.

Screenshots

Screenshot 1:

Additional Information

No response

@pictosun pictosun added the bug Something isn't working label Jan 30, 2025
@Chinaski1
Copy link
Member

Chinaski1 commented Jan 31, 2025

Hello there!

Could you please show examples of speed measurements?
And will there be a difference when using IPv4 and IPv6 addresses?

@pictosun
Copy link
Author

I think I found a reason for this. It is AS3320 - DTAG Networtk - maybe this is also the issue with problems over here #777

@pictosun
Copy link
Author

@Chinaski1 That's my AdGuardHome the last 24h

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants