50- windows xp pro workstations
1-2003 file server (192.168.0.250) w/ Active Directory (myagency.org)
1-Windows 2000 exchange server (192.168.0.249) w/ Active Directory (myagency.org)
To my knowledge neither server has DNS installed. Both servers referer to an external DNS for web for primary DNS. There are some minor AD replication problems between the two servers but thats a different problem
The problem here is that the xp workstations run GREAT when there primary IP is set to 192.168.0.249 (exchange server) but the just run ok when primary IP is set to 192.168.0.250 (2003 file server)
the workstations run SLOW when their primary IP is set directly to the external DNS 131.230.xxx.xxx
So I have decided to set the primary DNS to 192.168.0.249 and everyone is happy... except for 1 problem- the users with the ip of .249 (and .250 for that matter) cant see our companies website www.myagency.org
. They can see all other websites just fine but not ours. Our website is hosted somewhere else and the name of our website is the same as the name of our Domain.
So I am guessing that the clients are looking to my server for the address and when it is not there it says page not found, instead of going out to the web to look for it. Any suggestions on how to get my clients to be able to see our website? Thanks!!!!