Opened 5 months ago

Closed 5 months ago

#1191 closed request (fixed)

Cannot reach Quad9

Reported by: bortzmeyer+ietf@… Owned by: Clemens Schrimpe
Priority: tbd Milestone: ietf-100
Component: network Keywords:
Cc: warren@… My Current Location:
My MAC Address: My OS:

Description

Quad9 will be announced tomorrow but it cannot be reached from IETF
"ietf" SSID:

% traceroute -n 9.9.9.9
traceroute to 9.9.9.9 (9.9.9.9), 30 hops max, 60 byte packets
 1  31.133.128.2  13.056 ms  13.172 ms  13.193 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
...

It works from other networks (Quad9 is anycasted):

% traceroute -n 9.9.9.9
traceroute to 9.9.9.9 (9.9.9.9), 30 hops max, 60 byte packets
 1  10.1.5.2  0.441 ms  0.614 ms  0.670 ms
 2  209.66.115.109  0.671 ms  0.696 ms  0.679 ms
 3  * * *
 4  64.125.29.200  1.058 ms  1.207 ms  1.197 ms
 5  64.125.27.157  1.097 ms  1.152 ms  1.150 ms
 6  198.32.118.34  1.749 ms  2.130 ms  1.665 ms
 7  9.9.9.9  1.015 ms !X  0.992 ms !X  1.173 ms !X

Change history (10)

comment:1 Changed 5 months ago by llynch@…

Component: incomingnetwork
Owner: changed from < default > to jim@…
Status: newassigned

comment:2 in reply to:  2 ; Changed 5 months ago by bortzmeyer+ietf@…

On Wed, Nov 15, 2017 at 12:08:09AM -0000,
 IETF Tickets/NOC <tickets@meeting.ietf.org> wrote 
 a message of 25 lines which said:

>  Quad9 will be announced tomorrow but it cannot be reached from IETF
>  "ietf" SSID:

Note that their IPv6 prefix seems OK (same AS):

% traceroute6 2620:fe::9
traceroute to 2620:fe::9 (2620:fe::9) from 2001:67c:370:128:80b5:6b4e:7115:3002, 30 hops max, 24 byte packets
 1  rtra-wireless.meeting.ietf.org (2001:67c:370:128::2)  2.443 ms  10.344 ms  10.408 ms
 2  ge-100-0-0-3.r00.sngpsi05.sg.bb.gin.ntt.net (2001:218:4000:5000::1a5)  12.142 ms  18.431 ms  17.245 ms
 3  ae-0.a00.sngpsi05.sg.bb.gin.ntt.net (2001:218:0:2000::a)  42.854 ms  24.261 ms  9.769 ms
 4  ae-6.r01.sngpsi07.sg.bb.gin.ntt.net (2001:218:0:2000::d5)  10.803 ms  3.495 ms  17.275 ms
 5  ae-2.r21.sngpsi07.sg.bb.gin.ntt.net (2001:218:0:2000::76)  16.843 ms  3.222 ms  15.531 ms
 6  ae-2.r01.sngpsi03.sg.bb.gin.ntt.net (2001:218:0:2000::6)  12.867 ms  20.172 ms  17.047 ms
 7  ge-100-0-0-11.r01.sngpsi03.sg.ce.gin.ntt.net (2001:218:4000:5000::17a)  17.642 ms  4.61 ms  12.996 ms
 8  2620:fe::9 (2620:fe::9)  16.527 ms !S  15.952 ms !S  12.335 ms !S

comment:3 Changed 5 months ago by jim@…

Interestingly, we can't get to 9.9.9.9, but we can hit 9.9.9.10. This seems tied to one of our providers (Moratel). We're reaching out to them to try to fix this properly, but if it can't be resolved quickly, we'll filter the 9.9.9.0/24 route from them.

comment:4 Changed 5 months ago by jim@…

Owner: changed from jim@… to Clemens Schrimpe

comment:5 in reply to:  5 ; Changed 5 months ago by bortzmeyer+ietf@…

On Wed, Nov 15, 2017 at 01:39:39AM -0000,
 IETF Tickets/NOC <tickets@meeting.ietf.org> wrote 
 a message of 25 lines which said:

>  Interestingly, we can't get to 9.9.9.9, but we can hit
>  9.9.9.10. This seems tied to one of our providers (Moratel).

Many ISPs in Asia hijack the routing prefix of anycast DNS servers
(such as Google Public DNS). It may be the case here, they may have
added a special /32 route.

comment:6 Changed 5 months ago by Clemens Schrimpe

Cc: warren@… added
Status: assignedaccepted

Thanks for reporting this!

Mailed responsible uplink provider. Will get to you when we receive feedback.

comment:7 Changed 5 months ago by Clemens Schrimpe

Update: Provider working on it ...

comment:8 Changed 5 months ago by Clemens Schrimpe

Resolution: fixed
Status: acceptedclosed

Moratel had it blackholed - they investigate as to why.

Anyhow: It's fixed now!

comment:9 in reply to:  9 ; Changed 5 months ago by bortzmeyer+ietf@…

Resolution: fixed
Status: closedreopened
On Wed, Nov 15, 2017 at 03:17:30AM -0000,
 IETF Tickets/NOC <tickets@meeting.ietf.org> wrote 
 a message of 25 lines which said:

>  Anyhow: It's fixed now!

Confirmed. Thanks.


comment:10 Changed 5 months ago by jim@…

Resolution: fixed
Status: reopenedclosed
Note: See TracTickets for help on using tickets.