How to fix DNS timeout?

#1

C:\Users\Administrator>tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 17 ms 13 ms 80 ms 99.225.64.1
2 23 ms 23 ms 16 ms [67.231.221.225]
3 16 ms 11 ms 20 ms [209.148.231.209]
4 19 ms 8 ms 14 ms 209.148.235.34
5 * * * Request timed out.
6 13 ms 23 ms 213 ms one.one.one.one [1.1.1.1]

Trace complete.

C:\Users\Administrator>tracert 1.0.0.1

Tracing route to one.one.one.one [1.0.0.1]
over a maximum of 30 hops:

1 54 ms 11 ms 13 ms 99.225.64.1
2 18 ms 11 ms 14 ms 8077-dgw01.etob.rmgt.net.rogers.com [67.231.221.225]
3 10 ms 8 ms 5 ms 3009-cgw01.wlfdle.rmgt.net.rogers.com [69.63.248.181]
4 27 ms 12 ms 17 ms 209.148.235.141
5 * * * Request timed out.
6 19 ms 23 ms 195 ms one.one.one.one [1.0.0.1]

Trace complete.

#2

Thats not really a timeout. One hop on your trace doesnt respond, but that is not much of an issue.

Do you actually have any issues with the service?

2 Likes
#3

typically when there are time outs lag out from games etc so I dump the DNS and move to another DNS provider google opendns quad9 etc what ever is not timing out and going linkdead I just got these DNS have not done much testing with them just thought I would feedback them ideally you do not wanna use dns providers with any time outs unless you enjoy disconnects at random with out a really good reason today allot of video games ban for disconnects as well and these dns will cause that really nice

#4

Again, we are not talking about timeouts here.

Do you have issues with DNS?

#5

@ynp37594

There’s one hop timing out. (Backbone) Routers have one primary job: routing traffic. It’s not their job to answer to traces or ICMP requests. Probably this one is just busy with it’s job. Some are even configured not to reply at all. That doesn’t matter as long as the next HOP answers with reasonable times, like 1.1.1.1 in this case.

Sure, the third attempt took slightly longer with 213ms. But that does not cause time outs but might slow down DNS requests. To get proper results you should use tools like WinMTR and keep it running for 15 or 30 minutes.

They don’t run DNS requests to keep you in game. Sure they most likely will have DNS names configured to connect to their servers, but the address is resolved before your connection attemt. Anything after that is a direct IP connection. client-to-server.

It clould be a geo thing. Run this test

https://1.1.1.1/help

and post the link please.

#6

I just rebooted pc and could not connect to the internet until i removed cloudflare dns and replaced clouflare dns with anything except for cloudflare dns

the dns are configured via this program app
https://simplednscrypt.org/
makes it allot easier to find a random dns provider when I could not connect to the internet after selecting cloudflare dns and rebooting

i also never noticed the 200 ping in dns traces until mentioned here that is a really bad sign as well dial up pings start at around about 140

when I run this test in google chrome with cloudflare dns it says no dnssec support not secure and no SNI

cloudflares primary and secondary dns are both down at least for me anyways

google primary dns is down as well while googls alrenative dns is up and running

Tracing route to dns google [8.8.8.8]
over a maximum of 30 hops:

1 19 ms 16 ms 20 ms 99.225.64.1
2 8 ms 9 ms 10 ms 8077- [67.231.221.225]
3 16 ms 15 ms 16 ms 0-14-0-7- [209.148.232.137]
4 16 ms 22 ms 13 ms 209.148.233.38
5 13 ms 19 ms 12 ms 72.14.216.54
6 * * * Request timed out.
7 12 ms 16 ms 183 ms dns.google [8.8.8.8]

Trace complete.

C:\Windows\system32>tracert 8.8.4.4

Tracing route to dns google [8.8.4.4]
over a maximum of 30 hops:

1 15 ms 12 ms 217 ms 99.225.64.1
2 15 ms 12 ms 15 ms 8077- [67.231.221.225]
3 18 ms 16 ms 26 ms 0-5-0-7- [209.148.231.209]
4 17 ms 12 ms 17 ms 209.148.235.34
5 16 ms 16 ms 29 ms 72.14.222.87
6 15 ms 24 ms 12 ms 108.170.250.225
7 16 ms 12 ms 14 ms 108.170.226.219
8 14 ms 17 ms 13 ms dns.google [8.8.4.4]

Trace complete.

when looking for dns servers you only need command prompt and not crapware bloatware you ping the ip’s and look for bad pings and then you tracert the ip’s and look for time outs linkdeads any defects and you scrap the ip’s all together and look for another provider

while were at it lets take one more opendns cisco

Tracing route to [208.67.222.222]
over a maximum of 30 hops:

1 16 ms 12 ms 230 ms 99.225.64.1
2 20 ms 30 ms 13 ms 8077 [67.231.221.229]
3 12 ms 19 ms 27 ms 0-15-0-6 [209.148.232.141]
4 11 ms 4 ms 14 ms 209.148.235.30
5 30 ms 7 ms 143 ms [206.108.34.229]
6 17 ms 21 ms 21 ms [208.67.222.222]

Trace complete.

C:\Windows\system32>tracert 208.67.220.220

Tracing route to [208.67.220.220]
over a maximum of 30 hops:

1 14 ms 14 ms 175 ms 99.225.64.1
2 19 ms 14 ms 20 ms 8077- [67.231.221.229]
3 14 ms 20 ms 22 ms 0-15-0-6-cgw01. [209.148.232.141]
4 20 ms 14 ms 15 ms 209.148.235.30
5 15 ms 31 ms 12 ms [206.108.34.229]
6 17 ms 22 ms 20 ms [208.67.220.220]

Trace complete.

both of opendns dns servers by cisco fully work

#7

I am not sure which point you are trying to make.

Are you saying 1.1.1.1 does not work for you? If so you should run the checks mentioned at Have problems with 1.1.1.1? *Read Me First*