Question : DNS Round robin Server 2003

I am trying to setup DNS round robin and am getting a little stuck. I'm not an expert on DNS and require some help.

Our company has 3 webservers all setup on different IP ranges. All with different websites hosted on IIS6. I want to setup load balancing on the websites and DNS round robin seemed the easiest and cheapest way. Each websever is its own AD\DNS server in its own forest. All have server 2003 with at leat SP1 (we are also about to deploy Sever 2008 as well so please bear that in mind with your answer.) I've looked at various articles on the web but can't quite get my head around them. As it stands I  have a test website thats setup identically on 2 different websevers and I can hit one on it domain name and the other from its IP. The A record in the domain name settings points to 85.xx.xx.xx and this website is working ok.

From what I can gather DNS round robin is as easy as just adding a new A host record in the domain name settings. I've tried doing this and it never adds a new one. Just updates the old record. Unfortunatly the response from freeparking.com which the domain is with is ..

"Our dns manager does not support this function. You can only have 1 www record."

I'm I trying to do this correctly? And is their another way around this? As the severs stand I have not touched any DNS settings on the servers. They are just set as default.

Answer : DNS Round robin Server 2003

> Is that cached somewhere too?

Nope, that one is checked on each request.

It could be NetMask Ordering if you happen to be connecting from a very similar IP address?

Anyway, we can test it a bit.

Run:

nslookup www.roeville.com
nslookup www.roeville.com

We expect the list returned to change order with each alternate request. Like this:

Non-authoritative answer:
Name:    www.roeville.com
Addresses:  85.91.239.147, 85.91.239.163
...
Non-authoritative answer:
Name:    www.roeville.com
Addresses:  85.91.239.163, 85.91.239.147

See what I mean? That's round robin in operation.

You should see the same behaviour if you do:

ping www.roeville.com
ipconfig /flushdns
ping www.roeville.com
ipconfig /flushdns
etc

If that isn't happening, is the list being returned in the same order each time?

Chris