TP-Link ER707-M2 DNS PROBLEMS (RESOLVED)
I am having issues with DNS queries that are SLOW SLOW SLOW. I don't have IDS on and have connected to a OC300 which is working perfectly.
I have seen others complain of the LAG or slowness when handling DNS queries. That is the issue I am having, I wait 2-10 seconds for each request.
I owned this since June 25th and been fighting it daily since then.
I have gone back to my Fortinet router to rule out the router and it has no lag.
I have seen others complaining about slow dns with the ER605 series as well.
I have tried DNS direct with various dns servers, DNS caching via the router. It's just slow on the initial request.
--- edit ---
After throughly testing the DNS function and webchange output the router is indeed performing as it should. No speed issues found. I stand corrected.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @DACZ
Thanks for posting in our business forum.
The first query of the DNS is slow, how do you know that?
If the first query is slow, that's a problem with the latency.
If you use DoH, not plain DNS, that's a problem with the resolution to the DoH to find out the closest server.
It could be a problem with the latency of the ISP or the DoH that you used is not the proper one.
Very curious how do you verify that.
Overall, it gives me a feeling that this is a DNS server or an ISP latency issue. 2-10 seconds are thousands of milliseconds which means the latency is extremely obvious.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
do you use the router as a dns proxy or do you configure dns on the lan interface that the clients get?
if, for example, you set 1.1.1.2 and 1.0.0.2 on dhcp server on lan interface
if you set dns on the lan interface, it is not the router that does the dns lookup but the client and thus the router should not be the brake
- Copy Link
- Report Inappropriate Content
Hi @DACZ
Thanks for posting in our business forum.
The first query of the DNS is slow, how do you know that?
If the first query is slow, that's a problem with the latency.
If you use DoH, not plain DNS, that's a problem with the resolution to the DoH to find out the closest server.
It could be a problem with the latency of the ISP or the DoH that you used is not the proper one.
Very curious how do you verify that.
Overall, it gives me a feeling that this is a DNS server or an ISP latency issue. 2-10 seconds are thousands of milliseconds which means the latency is extremely obvious.
- Copy Link
- Report Inappropriate Content
From a DNS script and here are the results with the ER707-M2
Script being run from a Linux test box:
Test Domain Name
---- ---------------
t1: docker
t2: github
t3: gmail
t4: amazon
t5: apple
t6: facebook
t7: google
t8: paypal
t9: reddit
t10: twitter
t11: wikipedia
t12: yahoo
t13: youtube
Which results in as follows:
DNSSEC to Google (NO CACHE)
Provider t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 t12 t13 Median ms
--------------- --- --- --- --- --- --- --- --- --- --- --- --- --- ---------
LocalRouter * * 2 2 1 1 1 1 1 1 1 3 2 999 2-to
DOH to Cloudflare, as CloudFlare is the fasted from my location:
Provider t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 t12 t13 Median ms
--------------- --- --- --- --- --- --- --- --- --- --- --- --- --- ---------
LocalRouter 66 15 11 59 145 18 10 105 47 20 26 33 23 44.46 ms
CloudFlare/1 8 7 8 8 8 7 8 8 8 8 7 8 8 7.77 ms
DOT to Cloudflare
Provider t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 t12 t13 Median ms
--------------- --- --- --- --- --- --- --- --- --- --- --- --- --- ---------
Cloudflare/1 12 7 6 6 5 5 6 5 6 8 8 5 6 6.54 ms
LocalRouter 38 12 7 156 194 39 6 46 68 13 43 14 57 53.31 ms
DNSSEC to Cloudflare (NO CACHE)
Provider t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 t12 t13 Median ms
--------------- --- --- --- --- --- --- --- --- --- --- --- --- --- ---------
Cloudflare/1 9 8 6 5 10 5 5 5 6 10 6 5 5 6.54 ms
LocalRouter 39 38 25 60 224 67 15 291 27 35 53 76 36 75.85 ms
DNSSEC to Cloudflare (CACHE ENABLED)
Provider t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 t12 t13 Median ms
--------------- --- --- --- --- --- --- --- --- --- --- --- --- --- ---------
LocalRouter 38 40 25 58 217 21 14 168 29 69 44 38 35 61.23 ms
2nd RUN... (CACHED)
Provider t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 t12 t13 Median ms
--------------- --- --- --- --- --- --- --- --- --- --- --- --- --- ---------
LocalRouter 1 3 1 1 6 2 1 1 3 1 1 1 1 1.77 ms
3rd RUN... (CACHED)
Provider t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 t12 t13 Median ms
--------------- --- --- --- --- --- --- --- --- --- --- --- --- --- ---------
LocalRouter 1 3 1 1 1 1 2 1 1 1 1 1 1 1.23 ms
Which looks like it is working as it should.... I will do more testing with curl to load webpages and compare as it feels like there is a delay.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 497
Replies: 5
Voters 0
No one has voted for it yet.