We have a joint windows and netware environment. Prior to the windows domain environment being added for a feiw users, we pointed workstation DNS to our ISP's dns servers. No problems. With the advent of the windows AD environment, the Windows 2003 domain controller, also the DNS server, is now being used as the DNS controller for some of the users connected to the domain.
For testing, we have some other users, not logged into the domain, that are pointing to our Windows 2003 DNS server, 192.168.1.40. However, when we try to access www.microsoft.com
, it does not respond. Pinging it does not resolve the IP address (which does is we use one of the workstations that connects directly to our ISP's dns servers.
Also, if we try to access www.cnn.com
, it is real slow. Other external websites do not appear to be a problem. The gateway address 192.168.1.1 does pass through an IPRISM internet filtering/management device. All the other users that connect directly to the ISP's DNS, not being forwarded through the Windows 2003 DNS server, also go through the IPRISM device.
Any ideas on what is the problem or how to troubleshoot it?