I recently had to forgo using Cloudflare as DNS Resolver because for unexplained reasons it slowed down access to my Hotmail account (live version at http://outlook.com, and the live folders would not update except a a snail’s pace. I was able to correctly manage my Hotmail account live at http://outlook.com as soon as I had changed the DNS Server from Cloudflare to OpenDNS Home.
Any explanation, solution to this problem?
Robert
Can you try to ping 1.1.1.1 and the OpenDNS resolver IP? Also try pinging outlook.com while using 1.1.1.1 and OpenDNS.
1 Like
Hi Matteo,
First note that this is happening on a French system connecting to the Internet from France. Also note that slow down and hang up happen at other French sites but less frequently.
Pinging 1.1.1.1, then the OpenDNS resolver IP gave the following results:
Microsoft Windows [version 10.0.17763.253]
(c) 2018 Microsoft Corporation. Tous droits réservés.
C:\WINDOWS\system32>ping 1.1.1.1
Envoi d’une requête ‘Ping’ 1.1.1.1 avec 32 octets de données :
Réponse de 1.1.1.1 : octets=32 temps=33 ms TTL=53
Réponse de 1.1.1.1 : octets=32 temps=32 ms TTL=53
Réponse de 1.1.1.1 : octets=32 temps=32 ms TTL=53
Réponse de 1.1.1.1 : octets=32 temps=32 ms TTL=53
Statistiques Ping pour 1.1.1.1:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 32ms, Maximum = 33ms, Moyenne = 32ms
…
C:\WINDOWS\system32>ping 208.67.222.222
Envoi d’une requête ‘Ping’ 208.67.222.222 avec 32 octets de données :
Réponse de 208.67.222.222 : octets=32 temps=39 ms TTL=54
Réponse de 208.67.222.222 : octets=32 temps=39 ms TTL=54
Réponse de 208.67.222.222 : octets=32 temps=39 ms TTL=54
Réponse de 208.67.222.222 : octets=32 temps=39 ms TTL=54
Statistiques Ping pour 208.67.222.222:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 39ms, Maximum = 39ms, Moyenne = 39ms
Pinging outlook.com while using 1.1.1.1 gave the following results:
C:\WINDOWS\system32>ping outlook.com
Envoi d’une requête ‘ping’ sur outlook.com [40.97.160.2] avec 32 octets de données :
Réponse de 40.97.160.2 : octets=32 temps=184 ms TTL=231
Réponse de 40.97.160.2 : octets=32 temps=183 ms TTL=231
Réponse de 40.97.160.2 : octets=32 temps=183 ms TTL=231
Réponse de 40.97.160.2 : octets=32 temps=184 ms TTL=231
Statistiques Ping pour 40.97.160.2:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 183ms, Maximum = 184ms, Moyenne = 183ms
…
Pinging outlook.com while using the OpenDNS resolver gave the following results:
C:\WINDOWS\system32>ping outlook.com
Envoi d’une requête ‘ping’ sur outlook.com [40.97.153.146] avec 32 octets de données :
Réponse de 40.97.153.146 : octets=32 temps=114 ms TTL=237
Réponse de 40.97.153.146 : octets=32 temps=114 ms TTL=237
Réponse de 40.97.153.146 : octets=32 temps=114 ms TTL=237
Réponse de 40.97.153.146 : octets=32 temps=114 ms TTL=237
Statistiques Ping pour 40.97.153.146:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 114ms, Maximum = 114ms, Moyenne = 114ms
I don’t know if this is meaningful to you, but I can confirm that connection to Outlook, and in particular to its subsidiary ow2.res.office365.com, hangs most of the time when I use the Cloudflare DNS Server. There is never any problem connecting through OpenDNS Home (for example).
The thing I can see from here is that while using 1.1.1.1 there is an higher latency, I guess it goes to a farther server which can cause issues.
This is I guess an issue with the farther server (maybe the longer path causes issues or packet drops). Unfortunately it’s hard to diagnose here, maybe try opening a support ticket.
Also maybe @cloonan can pop in and see if internally they know of some issues.
I don’t see anything on a quick look but will investigate further. @crockett151283, can you open a ticket with support and post the number here, I’d like to get other eyes on this.
1 Like