[afnog] connection to www.cnn.com

[Brian Candler]

On Mon, Jun 05, 2006 at 04:46:54PM +0200, Mark Tinka wrote:
> > waiting for www.cnn.com
> 
> If you're getting this, at least we know cnn.com is replying to 
> you - this means they can reach you.

Maybe, but it depends exactly on the browser code and at what point it
updates its messages.

It could just mean that the name was resolved, the browser issued an
asynchronous connect() call and is waiting for the result. Maybe only the
outbound SYN packet was sent.

Or it might mean that a TCP 3-way exchange was established, but not with
www.cnn.com - if you have an upstream "transparent" web cache for example.

Messages from a browser are not good network debugging tools. You should get
your hands dirty with telnet and tcpdump.

BTW, I'm not sure if anyone mentioned reverse DNS - although I'd expect a
big site like cnn.com wouldn't be doing reverse lookups on incoming
requests. In any case, the reverse DNS for 41.220.0.4 looks OK to me.

However the name - customers.bushnet.net - implies to me that this is some
sort of proxy or gateway. Is the test actually originating from 41.220.0.4,
or from some machine behind it?

Regards,

Brian.