zespri:
Detruire:
What do those addresses resolve to for you (using nslookup and tracert)?
Sorry, which addresses? Of these sites?
Like this:
PS C:\WINDOWS\system32> nslookup stackoverflow.com
Server: router
Address: 192.168.88.1
Non-authoritative answer:
Name: stackoverflow.com
Addresses: 151.101.193.69
151.101.65.69
151.101.129.69
151.101.1.69
PS C:\WINDOWS\system32> nslookup www.trademe.co.nz
Server: router
Address: 192.168.88.1
Non-authoritative answer:
Name: www.trademe.co.nz
Address: 202.162.73.2
PS C:\WINDOWS\system32> tracert stackoverflow.com
Tracing route to stackoverflow.com [151.101.65.69]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms router [192.168.88.1]
2 23 ms 22 ms 22 ms 210.54.34.1
3 23 ms 23 ms 23 ms 122.56.60.68
4 23 ms 23 ms 24 ms 122.56.60.69
5 23 ms 21 ms 22 ms x1-1-1-200.akcr11.global-gateway.net.nz [122.56.118.89]
6 * * * Request timed out.
PS C:\WINDOWS\system32> tracert www.trademe.co.nz
Tracing route to www.trademe.co.nz [202.162.73.2]
over a maximum of 30 hops:
1 323 ms 226 ms 4 ms router [192.168.88.1]
2 194 ms 87 ms 76 ms 210.54.34.1
3 23 ms 23 ms 23 ms 122.56.60.68
4 23 ms 24 ms 23 ms 122.56.60.69
5 29 ms 22 ms 25 ms x1-1-1-200.akcr11.global-gateway.net.nz [122.56.118.89]
6 * * * Request timed out.
Yes. When I read Slingshot, my first thought was the broken DNS proxying in some of the routers they supply. I'd get some weird or missing DNS results, and ended up having to set the nameservers on each device to get around it. This doesn't look like the same thing, but that might be worth trying anyway (if you haven't already.)


