Hi dizzy, On Tue, Aug 19, 2008 at 5:55 PM, dizzy <dizzy@roedu.net> wrote:
On Sunday 17 August 2008 20:23:02 Dean Michael Berris wrote:
Well, doing 'host bucket.s3.amazonaws.com' from the shell works fine (it recognized that it's a virtualhost) so I don't think I was experiencing network problems then.
It only seems to occur with Boost.Asio's resolver implementation -- somehow it's not processing aliases correctly.
Works fine here: $ ./resolve bucket.s3.amazonaws.com 72.21.202.39
If you check with 'host', you should get: bucket.s3.amazonaws.com is an alias for s3-directional-w.amazonaws.com. s3-directional-w.amazonaws.com is an alias for s3-2-w.amazonaws.com. s3-2-w.amazonaws.com has address 207.171.191.252 Although doing reverse lookup using 'host 72.21.202.39', I get: 39.202.21.72.in-addr.arpa domain name pointer s3.amazonaws.com So I guess this might be a location-dependent thing, because when I reverse-lookup the IP I get (207.171.191.252): 252.191.171.207.in-addr.arpa domain name pointer 191-252.amazon.com At any rate, I've found a work-around specific to AmazonAWS which somehow works for me (which basically means ditching the alias syntax for the meantime). [snip] -- Dean Michael C. Berris Software Engineer, Friendster, Inc.