Question : URL not resolving to correct IP only on a few machines

We run a Windows Active Directory network with two DCs set up as DNS Servers. We have a few hundred users on the network divded among 4 subnets.The DCs are running 2003 R2 SP2 64 bit Windows. We have a handfull of XP machines running SP3 that intermittently can't seem to access a particular URL by name but can by IP. Others on the same subnet can with no problem . When I do an nslookup on the non working one it resolves to 2 IPs. When I do an nslookup on a working machine, it resolves to the same 2 IP addresses but the order is diifferent. One ip address works and the other does not.. On the machines with the problem, the first IP listed is the one that does not work. On the machines that work, the IP address that does not work is listed 2nd. I tried flushing the cache on the problem workstations as well as the DNS Servers.but no change. All the workstations are SP3 with the latest updates. Any suggestions would be greatly appreciated.

Answer : URL not resolving to correct IP only on a few machines

When you go to the DNS servers in your network (Microsoft I assume?)  and you look in the DNS plugin for the name, do you see multiple IP addresses?  UYou should ONLY have the local IP address in there.

Is that machine accessed from outside your local network?  (Dos it have a public and private IP address?)

If it does have a public address, does an external DNS server provide that (split DNS) or does your local DNS server have to provide the public IP address of the wen server?

If the internal DNS server does "double duty" and provides the external DNS as well, what you want to do it put ONLY the internal DNS address in the DNS and use the 'dns" feature of the PIX translate command to remap DNS information at the network border.

Most small networks use split DNS.

In either case, both DNS servers should ONLY list the ONE working address.

Us the public address returned yours, or someone elses?