Toujours ce matin :
Resolution via DNS google indiquant plusieurs non réponse mais se concluant par une réponse (IPv6) :
C:\Users\Administrator>nslookup google.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Name: google.com
Address: 2a00:1450:400c:c07::65
Et Ping KO puisque impossible de pinger l'IPv6 donnée car car je sors sur internet en IPv4 uniquement.
Resolution via OpenDNS :
C:\Users\Administrator>nslookup google.com 208.67.222.222
Server: resolver1.opendns.com
Address: 208.67.222.222
Non-authoritative answer:
Name: google.com
Addresses: 2a00:1450:4007:80d::200e
216.58.208.206
Ping KO suite resolution OpenDNS :
Tracing route to par10s21-in-f14.1e100.net [216.58.208.206]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.1
2 7 ms 10 ms 8 ms 10.123.0.1
3 12 ms 10 ms 7 ms 195-132-11-145.rev.numericable.fr [195.132.11.145]
4 22 ms 24 ms 23 ms 172.19.132.146
5 21 ms 21 ms 23 ms 72.14.196.224
6 22 ms 23 ms 23 ms 108.170.244.225
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
Resolution DNS via Cloudflare :
C:\Users\Administrator>nslookup google.com 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1
Non-authoritative answer:
Name: google.com
Addresses: 2a00:1450:4007:808::200e
216.58.213.174
Ping OK suite resolution via Cloudflare :
C:\Users\Administrator>tracert 216.58.213.174
Tracing route to par21s04-in-f14.1e100.net [216.58.213.174]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.1
2 9 ms 7 ms 7 ms 10.123.0.1
3 8 ms 7 ms 7 ms 195-132-11-145.rev.numericable.fr [195.132.11.145]
4 23 ms 23 ms 23 ms 172.19.132.146
5 21 ms 23 ms 21 ms 72.14.196.224
6 * * * Request timed out.
7 23 ms 21 ms 21 ms 64.233.175.195
8 21 ms 21 ms 21 ms par21s04-in-f14.1e100.net [216.58.213.174]
Trace complete.
Resolution via DNS NC :
Server: ns1.numericable.net
Address: 89.2.0.1
Non-authoritative answer:
Name: google.com
Addresses: 2a00:1450:4007:80f::200e
216.58.209.238
Ping KO suite resolution DNS NC :
Tracing route to par10s29-in-f238.1e100.net [216.58.209.238]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.1
2 7 ms 8 ms 6 ms 10.123.0.1
3 7 ms 7 ms 7 ms 195-132-11-145.rev.numericable.fr [195.132.11.145]
4 24 ms 23 ms 23 ms 172.19.132.146
5 20 ms 23 ms 21 ms 72.14.196.224
6 22 ms 21 ms 23 ms 108.170.244.225
7 21 ms 23 ms 21 ms 209.85.244.155
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * ^C
En bref :
8.8.8.8 me traduit google.com en IPv6 uniquement. Pas joignable depuis ma connexion car je sors en IPv4 uniquement.
1.1.1.1 me traduit google.com en IPv6 et IPv4, cette derniere IP est joignable.
89.2.0.1 traduit google.com en IPv6 et IPv4, cette derniere IP n'est pas joignable.
208.67.222.222 traduit google.com en IPv6 et IPv4, cette derniere IP n'est pas joignable non plus.
Dans tous les cas, les serveurs DNS utilisés sont joignables (Ping OK).
Conclusion : doit y avoir une route vers X réseau qui a sautée sur un routeur chez SFR-NC ...