To add a few more details to my previous email: * <account>.signin.aws.amazon.com is a CNAME for signin.aws.amazon.com. * signin.aws.amazon.com in turn resolves to various IP addresses (some sort of round-robin), some of which I *can* access over SSL and some of which I *cannot*. * Adding one of the working IP addresses to my hosts file takes me a step further and my browser redirects me to https://console.aws.amazon.com/console/home. * However, console.aws.amazon.com is completely inaccessible for me on port 443, regardless of which IP address I use from various lookups. Curiously, console.aws.amazon.com is a CNAME for an AWS US-east endpoint, so I'm starting to wonder if it's a connectivity issue between PLDT and US-east. Rob |
traceroute console.aws.amazon.com
traceroute to us-east-1.console.aws.amazon.com (72.21.215.152), 64 hops max, 52
byte packets
1 192.168.1.1 (192.168.1.1) 4.582 ms 3.240 ms 3.564 ms
2 112.209.96.1.pldt.net (112.209.96.1) 16.911 ms 16.978 ms 19.978 ms
3 119.93.255.213 (119.93.255.213) 20.238 ms 16.049 ms 16.617 ms
4 210.213.132.34.static.pldt.net (210.213.132.34) 14.542 ms 14.272 ms
210.213.132.38.static.pldt.net (210.213.132.38) 16.572 ms
5 210.213.128.53.static.pldt.net (210.213.128.53) 15.888 ms 15.906 ms
17.997 ms
6 210.213.133.5.static.pldt.net (210.213.133.5) 18.257 ms 18.111 ms 16.502
ms
7 * * *
8 * * *
9 * * *
10 * * *
...
On Nov 19, 2013, at 7:41 AM, fooler mail <[email protected]> wrote:
|
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph

