On Thu, 16 Apr 2009, e deleflie wrote:
> Hugh,
>
> (BTW, thanks for your patience and help).
>
> I just logged into windows (native) and connected to the Internet via
> a different modem (that gets DNS servers dynamically). This is what I
> get:
>
> C:\Documents and Settings\etienne>nslookup blabla.blabla.s3.amazonaws.com
> DNS request timed out.
> timeout was 2 seconds.
> *** Can't find server name for address 202.124.68.130: Timed out
> *** Can't find server name for address 202.124.76.98: Non-existent domain
I think that means it's checked for all the servers it knows about....
> *** Default servers are not available
...but this "not available" message is rather ambiguous.
> Server: UnKnown
> Address: 202.124.68.130
>
> Non-authoritative answer:
> Name: s3-2-w.amazonaws.com
> Address: 207.171.185.195
> Aliases: ambiboots.audio.s3.amazonaws.com
> s3-directional-w.amazonaws.com
So it got an answer from somewhere. DNS cache? I don't know.
>
> -----------------------
> I cant easily get people to try the code, because to access amazon's
> S3 (to do a POST) I need to first get a 'signed url' (a
> time-restricted authenticated url for posting) from my own server ...
> and THEN with that signed url I can do the post to S3.
Can you just release similar code that gets something simple from
your server, but in such a way that the DNS is prodded in the
same way you do at the moment which may or may not fail?
>
> Although, I guess I could show you the code.
>
> An other option is that I just 'package' the app and let people try it
> in the full blown context ...
Well, its a good idea to isolate problems to one part if one can.
>
> Etienne
>
Hugh
