Browser DNS balancing effects
- From: Theo Markettos <theom+news@xxxxxxxxxxxxxxxxxxxxxx>
- Date: 23 Jun 2008 12:29:26 +0100 (BST)
I'm trying to work the login process to a website automatically, using
curl's cookie support. So I fire off multiple curl commands which make use
of the same cookie jar, one to the login page, one with my username and
password, and then some more to the site after I've logged in.
What I've noticed is that occasionally the site returns back 'Session lost'
errors at random, claiming that my session has expired when I've only just
logged in. I'm definitely sending the cookie that it gave me.
This doesn't ever happen with a web browser. I notice the DNS entry for the
site is similar to:
login.example.com. 588 IN A 1.2.3.4
login.example.com. 588 IN A 5.6.7.8
It could be that my curl requests are hitting a different server each time,
and there isn't any login-coherency between the two servers (so the cookie
sent by 1.2.3.4 isn't recognised if I send it to 5.6.7.8). It's not the
best written of sites, so this wouldn't surprise me.
So what I wondered is how do browsers handle the case of multiple A records?
Do they pick one and use it for all transactions to that site? Is that
defined behaviour? I know some browsers have their own DNS caching, but
does this cache one or both of the A records? Does they (I'm testing with
mostly Mozilla-based browsers) pick one address but expire it after the TTL?
I read that some browsers ignore the TTL and have their own timeout (to
avoid DNS poisoning), but how does this interact with multiple A records?
Thanks
Theo
.
- Follow-Ups:
- Re: Browser DNS balancing effects
- From: Robert Billing
- Re: Browser DNS balancing effects
- From: C.
- Re: Browser DNS balancing effects
- From: Patter
- Re: Browser DNS balancing effects
- Prev by Date: Re: Partitioning hard drives...
- Next by Date: Re: Partitioning hard drives...
- Previous by thread: Partitioning hard drives...
- Next by thread: Re: Browser DNS balancing effects
- Index(es):
Relevant Pages
|