Packetloss / nextdns?

Question

Heb in de meern (glasvezel, WBA) afgelopen maand issue met NextDNS. Omdat al mijn internet verkeer hier heen gaat en er veel packetloss of hoge latencies vallen zelfs accesspoints uit en apps, websites kunnen niet meer resolven. Ook thuiswerken is af en toe onmogelijk.

Bij de NextDNS-cli zit ik ook allemaal meldingen

Apr 23 09:58:53 ubnt nextdnsn7173]: Control client connected: &{{0x40002d0180}}
Apr 23 09:58:53 ubnt nextdnsn7173]: Control client sent event: &{{0x40002d0180}}: trace(<nil>)
Apr 23 09:58:53 ubnt nextdnsn7173]: Control client disconnected: &{{0x40002d0180}}
Apr 23 10:04:08 ubnt nextdnsn7173]: Connected 45.90.30.0:443 (con=5ms tls=288ms, TCP, TLS13)
Apr 23 10:04:08 ubnt nextdnsn7173]: Connected 95.179.134.211:443 (con=6ms tls=173ms, TCP, TLS13)
Apr 23 10:04:08 ubnt nextdnsn7173]: Switching endpoint: https://dns.nextdns.io#188.172.219.167,2a00:11c0:63:350::3,95.179.134.211,2001:19f0:5001:1faf:5400:2ff:fec8:7d49
Apr 23 10:06:48 ubnt nextdnsn7173]: Connected 188.172.219.167:443 (con=5ms tls=9ms, TCP, TLS13)
Apr 23 10:08:21 ubnt nextdnsn7173]: Connected 188.172.219.167:443 (con=5ms tls=7ms, TCP, TLS13)
Apr 23 10:10:55 ubnt nextdnsn7173]: Connected 188.172.219.167:443 (con=5ms tls=10ms, TCP, TLS13)
Apr 23 10:16:14 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:15 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:15 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:15 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:15 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:15 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:15 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:16 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:16 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:16 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:16 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:16 ubnt nextdnsn7173]: Connected 95.179.134.211:443 (con=5ms tls=151ms, TCP, TLS13)
Apr 23 10:16:16 ubnt nextdnsn7173]: Switching endpoint: https://dns.nextdns.io#95.179.134.211,2001:19f0:5001:1faf:5400:2ff:fec8:7d49,188.172.219.167,2a00:11c0:63:350::3
Apr 23 10:16:17 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:17 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:17 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:17 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:17 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:18 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:18 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:18 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:18 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:18 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:19 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:19 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:19 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:19 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:20 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:20 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:20 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:20 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:20 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:21 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:21 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:16:21 ubnt nextdnsn7173]: Query 162.254.192.87 UDP TXT VERSION.BIND. (qry=30/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
Apr 23 10:25:38 ubnt nextdnsn7173]: Connected 95.179.134.211:443 (con=6ms tls=8ms, TCP, TLS13)

traceroute:

traceroute to 45.90.30.0 (45.90.30.0), 30 hops max, 46 byte packets 1  1-208-201-31.ftth.glasoperator.nl (31.201.208.1)  2.139 ms  2.066 ms  1.758 ms 2  10.10.10.213 (10.10.10.213)  4.906 ms  4.857 ms  4.810 ms 3  10.10.12.53 (10.10.12.53)  4.821 ms  4.925 ms  4.844 ms 4  80.249.212.38 (80.249.212.38)  11.012 ms  10.377 ms  7.007 ms 5  10.72.2.6 (10.72.2.6)  7.787 ms  6.511 ms  6.478 ms 6  10.72.16.2 (10.72.16.2)  5.502 ms  5.508 ms  10.72.16.6 (10.72.16.6)  6.151 ms 7  *  *  * 8  *  *  * 9  *  *^C# traceroute 95.179.134.211traceroute to 95.179.134.211 (95.179.134.211), 30 hops max, 46 byte packets 1  1-208-201-31.ftth.glasoperator.nl (31.201.208.1)  1.805 ms  1.775 ms  1.856 ms 2  10.10.10.213 (10.10.10.213)  4.899 ms  4.929 ms  4.822 ms 3  10.10.12.53 (10.10.12.53)  4.918 ms  4.920 ms  4.900 ms 4  80.249.212.38 (80.249.212.38)  6.419 ms  6.027 ms  6.518 ms 5  10.72.2.6 (10.72.2.6)  6.553 ms  6.521 ms  11.668 ms 6  10.72.16.6 (10.72.16.6)  5.991 ms  5.908 ms  6.054 ms 7  *  *  * 8  *  *  * 9  *  *  *10  *  *  *11  *  *  *12  *  *  *13  *  *  *14  *  *  *15  *  *  *16  *  *  *17  *  *  *18  *  *  *19  *  *  *20  *  *  *21  *  *  *22  *  *  *23  *  *  *24  *  *  *25  *  *  *26  *  *  *27  *  *  *28  *  *  *29  *  *  *30  *  *  *

Wie weet wat er aan de hand is en hoe dit opgelost kan worden?

Anonymous · Accepted Answer

Hi @vaevictis,Probeer eens de diagnose tool van NextDNS te gebruiken om te zien wat er gebeurd. Je kan dan ook het resultaat naar hun uploaden zodat zij vanuit hun kant kunnen kijken.https://nextdns.io/diag

Waqqas · Answer

Hallo @vaevictisGebruik je hier een eigen router bij? Misschien kan je eens kijken of het helpt om de T-Mobile modem met standaard DNS servers te gebruiken?

Niet gevonden wat je zocht?

Meld je aan

Welkom

Bestand scannen voor virussen

Dit bestand kan niet worden gedownload