Round Robin DNS and Session Cookies- Will this work on a web server?

Hi there,

We are looking for a simple way to add redundancy to a web app.
We are concerned about session cookies.

If we just put each server on a round robin DNS service, will that be sufficient at least for our beta release or will session cookies be a big issue?

I'm guessing that the user caches the DNS of the server and in such a case I would expect that problems are rare. But I could imagine that when they are on the site for over 15 minutes (assuming the DNS refresh is set to 15 minutes) then it will cause big problems.

IDEALLY: Is there a round robin DNS service that is designed for failover and will always redirect the same IP to the same server?

As a work-around, we are thinking: Since we have a centralized database, we centrally save all session data. Then, when a user without a session cookie is found, we check if it exists and log them in.
the_cymanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Bruno PACIIT ConsultantCommented:
Hi,

In the Microsoft world what you're looking for is called NLB cluster (Network Load Balancing). That's the way I would reach the goal if the Web servers are Miscrosoft IIS servers.

I don't know much about non-microsoft worl but surely DNS round robin will not do the job because when you DNS client cache expires you could be routed to a web server that doesn't know anything about you current session (except if you have a process inside your application that can replicate session contexte between web servers).

When you configure NBL cluster you can do thing so that one client IP address will always be routed to one NLB cluster node.

Have a nice day
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bevhostCommented:
If the cookie session data is stored in a central database, I don't see how it matters which front end server processes each of the http: requests?

You can use BIND 9 DNS server to always hand the same IPs out to selected clients but that's not really round robin.
0
Colin_A_MoulderCommented:
What I would use is Microsoft NLB and Distributed File System to point towards a central depository of web files that can also be updated concurrently.
As for session cookies, it is not an issue because you will be contacting the websites via the NLB cluster address and using host headers.
 
0
the_cymanAuthor Commented:
Great, thanks guys. Looks like there are services like this one:
http://www.autofailover.com/
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.