Interesting dns

Not applicable

I have been doing a trace route to www.shaw.ca 3 times in a row and got 3 different results.

This is highly confusing to me. www.shaw.ca works fine in any web browser so it is pointing to the correct location.

I use 8.8.8.8 as primary and 1.1.1.1 as secondary DNS server.

Below are the routes. Why are they like that?

C:\Users\xxxx>tracert www.shaw.ca

Tracing route to e3863.g.akamaiedge.net [104.88.10.134] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms untangle.gateway.com [192.168.1.1]
2 10 ms 6 ms 9 ms x.x.x.x
3 10 ms 10 ms 7 ms 24.244.8.141
4 17 ms 19 ms 16 ms rc4fs-tge0-14-0-15.mt.shawcable.net [66.163.75.170]
5 28 ms 26 ms 26 ms rc3ec-be10.il.shawcable.net [66.163.65.6]
6 25 ms 26 ms 27 ms ae-1.a00.chcgil09.us.bb.gin.ntt.net [168.143.229.37]
7 41 ms 42 ms 42 ms ae-21.r08.chcgil09.us.bb.gin.ntt.net [129.250.3.158]
8 * 30 ms 42 ms ae-0.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.191]
9 44 ms 44 ms 44 ms ae-0.r25.nycmny01.us.bb.gin.ntt.net [129.250.2.167]
10 43 ms 42 ms 42 ms ae-2.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.98]
11 54 ms 50 ms 47 ms ae-0.a00.nycmny01.us.bb.gin.ntt.net [129.250.3.94]
12 43 ms 44 ms 43 ms a104-88-10-134.deploy.static.akamaitechnologies.com [104.88.10.134]

Trace complete.

C:\Users\xxxx>tracert www.shaw.ca

Tracing route to e3863.g.akamaiedge.net [104.88.10.134] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms untangle.gateway.com [192.168.1.1]
2 7 ms 8 ms 6 ms x.x.x.x
3 7 ms 8 ms 9 ms 24.244.8.141
4 23 ms 22 ms 19 ms rc4fs-tge0-14-0-15.mt.shawcable.net [66.163.75.170]
5 26 ms 26 ms 26 ms rc3ec-be10.il.shawcable.net [66.163.65.6]
6 25 ms 26 ms 26 ms ae-1.a00.chcgil09.us.bb.gin.ntt.net [168.143.229.37]
7 43 ms 43 ms 42 ms ae-21.r08.chcgil09.us.bb.gin.ntt.net [129.250.3.158]
8 26 ms 26 ms 29 ms ae-0.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.191]
9 44 ms 43 ms 43 ms ae-0.r25.nycmny01.us.bb.gin.ntt.net [129.250.2.167]
10 43 ms 43 ms 42 ms ae-2.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.98]
11 44 ms 44 ms 44 ms ae-0.a00.nycmny01.us.bb.gin.ntt.net [129.250.3.94]
12 43 ms 43 ms 47 ms a104-88-10-134.deploy.static.akamaitechnologies.com [104.88.10.134]

Trace complete.

C:\Users\Droopy>tracert www.shaw.ca

Tracing route to e3863.g.akamaiedge.net [104.117.6.17] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms untangle.gateway.com [192.168.1.1]
2 7 ms 9 ms 9 ms 70.76.32.1
3 8 ms 7 ms 7 ms 24.244.8.141
4 16 ms 18 ms 15 ms rc4fs-tge0-14-0-15.mt.shawcable.net [66.163.75.170]
5 27 ms 26 ms 26 ms rc3ec-be10.il.shawcable.net [66.163.65.6]
6 27 ms 26 ms 25 ms ae-1.a00.chcgil09.us.bb.gin.ntt.net [168.143.229.37]
7 50 ms 52 ms 49 ms ae-21.r08.chcgil09.us.bb.gin.ntt.net [129.250.3.158]
8 26 ms 27 ms 26 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
9 47 ms 47 ms 46 ms ae-1.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.138]
10 46 ms 48 ms 46 ms ae-2.r05.asbnva02.us.bb.gin.ntt.net [129.250.2.22]
11 47 ms 48 ms 59 ms ae-0.a00.asbnva02.us.bb.gin.ntt.net [129.250.5.152]
12 79 ms 58 ms 67 ms ae-0.akamai-onnet.asbnva02.us.bb.gin.ntt.net [129.250.195.214]
13 50 ms 48 ms 47 ms a104-117-6-17.deploy.static.akamaitechnologies.com [104.117.6.17]

Trace complete.

Labels (1)
7 Replies

Re: Interesting dns

Moderator
Moderator

Hey vanadiel,

Thank you for reaching out! I notice that you did mention you have 1.1.1.1 as your secondary DNS. Looks like that is going through Cloudflare based on that DNS? I do see that when you run the trace it shows that it is going through e3863.g.akamaiedge.net [104.88.10.134]. What happens when you remove the secondary DNS, does it still show the same results? 

Also, do you have any 3rd party routers or switches attached to the Shaw modem with special settings like a VPN?

Thanks,

Tony | Community Mod.

0 Kudos
Reply
Loading...

Re: Interesting dns

Not applicable

I set the second DNS to 64.59.176.13, Shaw's primary DNS for Ontario.

No VPN services used, and all others show normal routes.

Did a few more tracert, only www.shaw.ca seems to have an odd route.

Speedtest.shaw.ca is normal.

The route for www.shaw.ca today is different than yesterday (hwgn.net instead of ntt.net)

It is bizarre...

Tracing route to e3863.g.akamaiedge.net [23.197.161.165] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms untangle.gateway.com [192.168.1.1]
2 7 ms 8 ms 6 ms 70.76.32.1
3 10 ms 11 ms 9 ms 24.244.8.141
4 16 ms 15 ms 15 ms rc4fs-tge0-14-0-15.mt.shawcable.net [66.163.75.170]
5 18 ms 23 ms 19 ms rc3fs-be5.mt.shawcable.net [66.163.66.57]
6 29 ms 31 ms 28 ms rc1eqn-tge0-0-0-0.uk.shawcable.net [66.163.78.146]
7 30 ms 30 ms 31 ms 66.163.74.18
8 35 ms 28 ms 28 ms paix-ny.3-2.r1.ny.hwng.net [198.32.118.76]
9 44 ms 44 ms 47 ms ae4.r2.ch.hwng.net [209.197.0.33]
10 44 ms 45 ms 45 ms 209.197.20.32
11 55 ms 45 ms 44 ms 209.197.20.177
12 45 ms 44 ms 46 ms a23-197-161-165.deploy.static.akamaitechnologies.com [23.197.161.165]

Trace complete.

C:\Users\xxxx>tracert www.google.com

Tracing route to www.google.com [172.217.13.164] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms untangle.gateway.com [192.168.1.1]
2 7 ms 10 ms 7 ms 70.76.32.1
3 7 ms 7 ms 7 ms 24.244.8.141
4 18 ms 19 ms 18 ms rc4fs-tge0-14-0-15.mt.shawcable.net [66.163.75.170]
5 16 ms 15 ms 15 ms 72.14.196.237
6 16 ms 16 ms 19 ms 108.170.250.226
7 26 ms 23 ms 23 ms 216.239.46.114
8 24 ms 23 ms 25 ms 108.170.251.33
9 23 ms 23 ms 33 ms 108.170.231.63
10 22 ms 23 ms 23 ms yul03s04-in-f4.1e100.net [172.217.13.164]

Trace complete.

C:\Users\xxxx>tracert speedtest.shaw.ca

Tracing route to speedtest.glb.shawcable.net [64.59.134.43] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms untangle.gateway.com [192.168.1.1]
2 8 ms 6 ms 11 ms 70.76.32.1
3 7 ms 17 ms 12 ms 24.244.8.141
4 12 ms 8 ms 8 ms 66.163.66.77
5 27 ms 27 ms 26 ms rc2nr-tge0-10-0-30.wp.shawcable.net [66.163.73.213]
6 43 ms 44 ms 43 ms rc3no-be110-1.cg.shawcable.net [66.163.76.57]
7 44 ms 45 ms 44 ms 64.59.135.238
8 47 ms 43 ms 47 ms 64.59.134.43

Trace complete.

0 Kudos
Reply
Loading...

Re: Interesting dns

Not applicable

To add to the confusion, you even get strange results when using external tools to check www.shaw.ca

I used *removed external link*

The A record points to exactly where mine points to: 23.52.52.166 (e3863.g.akamaiedge.net)

The CNAME record points to shawca.edgekey.net

I also used *removed external link*

Same results:

  184.50.175.181
Cambridge, MA, United States
RDNS: a184-50-175-181.deploy.static.akamaitechnologies.com
Provider: Akamai Technologies

And I also used *removed external link*

id 37709 opcode QUERY rcode NOERROR flags QR RD RA ;QUESTION www.shaw.ca. IN A ;ANSWER www.shaw.ca. 176 IN CNAME shawca.edgekey.net. shawca.edgekey.net. 21476 IN CNAME e3863.g.akamaiedge.net. e3863.g.akamaiedge.net. 19 IN A 23.7.51.110 ;AUTHORITY ;ADDITIONAL

 

0 Kudos
Reply
Loading...

Re: Interesting dns

Moderator
Moderator

vanadiel that is very odd. Are you testing this on a PC attached to a Shaw Internet modem? What do you receive when you run the same tests on a mobile device on an LTE/4G/3G network?

0 Kudos
Reply
Loading...

Re: Interesting dns

Not applicable

I tried with my phone using my providers network, same thing. That one does not use the Shaw network but a different network as you can see in the traceroute.

I tried with a few different programs on my phone to ensure it's correct and they all show the same thing.

Traceroute of phone below to www.shaw.ca

1. 172.25.44.237; 68.8, 68.7, 69.6

2. 172.25.53.17; *, *, *

3. 172.25.53.114; *, *, *

4. 172.25.196.146; *, *, *

5. 204.101.5.157; 407, 407, 447

6. *

7. *

8. *

9. *

10. *

11. 104.102.66.134; a104-102-66-134.deploy.static.akamaitechnologies.com; 54.1, 71.3, 69.1

So it's not me.

When I did the traceroute today from my computer using Shaw, the route has  changed and it looks like Shaw is now routing directly with the destination server, which is now a different IP but still part of akamaiedge.net

C:\Users\xxxx>tracert www.shaw.ca

Tracing route to e3863.g.akamaiedge.net [23.6.244.56]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms untangle.gateway.com [192.168.1.1]
2 11 ms 14 ms 8 ms 70.76.x.x
3 12 ms 10 ms 9 ms 24.244.8.141
4 10 ms 11 ms 9 ms 66.163.66.77
5 29 ms 27 ms 27 ms rc2nr-tge0-10-0-30.wp.shawcable.net [66.163.73.213]
6 45 ms 46 ms 45 ms rc3no-be110-1.cg.shawcable.net [66.163.76.57]
7 56 ms 58 ms 56 ms rc1st-be11-1.vc.shawcable.net [66.163.72.70]
8 58 ms 57 ms 58 ms rc1bb-tge0-0-0-28.vc.shawcable.net [66.163.69.197]
9 58 ms 58 ms 56 ms a23-6-244-56.deploy.static.akamaitechnologies.com [23.6.244.56]

Trace complete.

I am going to do a traceroute from my work tomorrow. They use yet another provider and they are a large corporate network so there's no way they would have anything super strange going on.

If that traceroute shows the same results as mine than it has to be correct.

0 Kudos
Reply
Loading...

Re: Interesting dns

Not applicable

Are you sure Shaw does not use Akamai Fast DNS for www.shaw.ca to avoid ddos attacks and other issues?

Because I am pretty sure that is what is going on.

0 Kudos
Reply
Loading...

Re: Interesting dns

Moderator
Moderator

vanadiel my apologies! Looks like you are correct. I ran a few new traceroutes today and see that we do route through them. Everything should be working as intended. Let me know if you have any other questions! 

0 Kudos
Reply
Loading...
TALK TO US
Need more help?