I have not been able to use specific websites after installing an edgerouter X on my century link fiber service. The router has just the bare minimum VLAN 201 + PPPoE Authentication configured for its WAN. Most websites work fine. A few websites hosted by Microsoft azure don't seem to connect. This issue does not occur with the Century Link provided router.
As you can see in this traceroute, Century Link is handing my traffic over to Microsoft, so it does not appear the issue is on Century Link's end.
Tracing route to duckduckgo.com [52.149.246.39] over a maximum of 30 hops: 1 2 ms 11 ms 7 ms 192.168.2.1 2 4 ms 9 ms 3 ms boid-dsl-gw18.boid.qwest.net [184.99.64.18] 3 6 ms 6 ms 6 ms boid-agw1.inet.qwest.net [184.99.65.137] 4 16 ms 14 ms 31 ms ae27.edge6.Seattle1.Level3.net [4.68.63.133] 5 * * * Request timed out. 6 15 ms 14 ms 16 ms Microsoft-level3-10G.Seattle1.Level3.net [4.71.156.74] 7 23 ms 56 ms 25 ms ae25-0.icr01.mwh01.ntwk.msn.net [104.44.233.82] 8 72 ms 160 ms 72 ms be-160-0.ibr02.mwh01.ntwk.msn.net [104.44.21.149] 9 73 ms 73 ms 74 ms be-7-0.ibr02.cys04.ntwk.msn.net [104.44.18.224] 10 85 ms 163 ms 98 ms be-8-0.ibr02.dsm05.ntwk.msn.net [104.44.18.151] 11 72 ms 100 ms 111 ms be-4-0.ibr02.ch2.ntwk.msn.net [104.44.19.252] 12 73 ms 75 ms 73 ms 104.44.29.252 13 72 ms 72 ms 74 ms 104.44.30.5 14 74 ms 71 ms 71 ms 104.44.32.47 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out.
This occurs with all DNS resolutions to duckduckgo.com I have tried (including google public dns, century link's dns, opendns, cloudflare, etc.)
I think my IP might just be banned in Azure Cloud or something. Unfortunately I have not been able to get a new one assigned. Rebooting all on premises equipment and explicitly diconnecting/reconnecting the PPPoE interface does not assign a new IP.
No comments:
Post a Comment