Change your DNS server to a public one other than Snap. I'm using Google's public DNS server 8.8.8.8 temporarily.
Obviously though it means if you have the all you can eat Youtube, it probably won't be considered under the all you can eat as it won't go through Snap's Google cache if using someone else's DNS.
So remember to change DNS back in Windows to Snap's again as soon as they resolve the routing issue.
Gavin.
edit: you may need to open a command line, and type: ipconfig /flushdns after changing DNS ip addresses to flush any cached IP's so it will send a new request to the new DNS server.
Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Tracing route to facebook.com [66.220.158.11] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms RTA1320.home [192.168.1.1] 2 17 ms 16 ms 16 ms 16.17.69.111.static.snap.net.nz [111.69.17.16] 3 16 ms 16 ms 16 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54] 4 16 ms 16 ms 16 ms 111-69-27-65.core.snap.net.nz [111.69.27.65] 5 21 ms 16 ms 16 ms 203.167.233.10 6 152 ms 152 ms 152 ms i-0-6-4-0.tlot-core01.bx.reach.com [202.84.142.110] 7 151 ms 151 ms 151 ms i-2-6.tlot03.bi.reach.com [202.84.251.150] 8 152 ms 151 ms 151 ms facebook.com.any2ix.coresite.com [206.223.143.161] 9 185 ms 185 ms 185 ms xe-1-3-0.br01.dfw1.tfbnw.net [204.15.21.7] 10 217 ms 205 ms 205 ms xe-4-0-0.bb02.atl1.tfbnw.net [204.15.23.64] 11 217 ms 217 ms 217 ms ae22.bb02.iad2.tfbnw.net [204.15.20.99] 12 216 ms 216 ms 216 ms ae8.dr02.ash4.tfbnw.net [74.119.77.214] 13 216 ms 216 ms 216 ms po509.csw01b.ash4.tfbnw.net [74.119.78.253] 14 215 ms 215 ms 214 ms facebook.com [66.220.158.11]
Trace complete.
Tracing route to static.ak.fbcdn.net [202.124.127.106] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms RTA1320.home [192.168.1.1] 2 16 ms 16 ms 16 ms 16.17.69.111.static.snap.net.nz [111.69.17.16] 3 15 ms 16 ms 16 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54] 4 31 ms 31 ms 31 ms 111-69-3-220.core.snap.net.nz [111.69.3.220] 5 33 ms 31 ms 33 ms 111-69-3-221.core.snap.net.nz [111.69.3.221] 6 31 ms 38 ms 31 ms 106.127.124.202.static.snap.net.nz [202.124.127.106]
Trace complete.
Tracing route to www.smd.com.au [210.8.240.26] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms RTA1320.home [192.168.1.1] 2 16 ms 16 ms 16 ms 16.17.69.111.static.snap.net.nz [111.69.17.16] 3 15 ms 30 ms 15 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54] 4 38 ms 16 ms 16 ms 111-69-27-65.core.snap.net.nz [111.69.27.65] 5 16 ms 16 ms 16 ms 203.167.233.10 6 40 ms 40 ms 40 ms i-0-0-4-0.sydo-core02.bx.reach.com [202.84.142.153] 7 42 ms 41 ms 41 ms i-0-5-4-0.sydp-core01.bi.reach.com [202.84.249.13] 8 44 ms 43 ms 44 ms TenGigE0-2-0-7.pad-gw1.Sydney.telstra.net [203.50.13.81] 9 46 ms 47 ms 48 ms Bundle-Ether3.chw-core2.Sydney.telstra.net [203.50.6.26] 10 42 ms 45 ms 42 ms TenGigabitEthernet7-1.chw38.Sydney.telstra.net [203.50.20.176] 11 42 ms 42 ms 42 ms aaptli3.lnk.telstra.net [110.142.0.194] 12 57 ms 57 ms 57 ms te2-4.sglebdist02.aapt.net.au [202.10.14.8] 13 54 ms 54 ms 54 ms te2-1-110.sglebdist01.aapt.net.au [202.10.12.130] 14 54 ms 54 ms 54 ms te0-3-4-0.sglebcore01.aapt.net.au [202.10.12.7] 15 57 ms 57 ms 56 ms te0-0-0-0.bqueecore01.aapt.net.au [202.10.10.66] 16 162 ms 110 ms 56 ms te2-2.bforvdist02.aapt.net.au [202.10.12.24] 17 56 ms 56 ms 56 ms gi0-3.qbrifcust09.aapt.net.au [202.10.13.75] 18 57 ms 57 ms 57 ms INT133405-4.gw.connect.com.au [203.63.65.157] 19 57 ms 57 ms 57 ms www.smd.com.au [210.8.240.26]
Trace complete.
Is it just me or is "14 215 ms 215 ms 214 ms facebook.com [66.220.158.11]" 256ms a big delay ?
I've just jumped on to the smh site since I got back in and it loaded with Snap's DNS settings.
I think my DSL router might be falling over in a weird and spectacular way. I might have been chasing two red hearings since Tuesday. It took getting booted from Snap to rear it's other problem.
I found another site that wouldn't work this time it didn't resolve to a Snap address, so I think the DSL router's kicking the bucket.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
