Discussion Locked

Internal DNS Problems

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are currently migrating our workstations from NT 4.0 to Windows 2000. We have a Windows 2000 internal DNS server that is just used for resolving URL?s, we are not using Active Directories.

Our users are reporting problems getting to our websites internally. When I go to their desk, and do an nslookup to the URL the internal DNS server resolves the URL to the internal address on our network. But when I ping the URL it resolves to the outside address. Our firewall is blocking the traffic, so our users are forced to use the internal address.

The users who have not been converted to Windows 2000 have no problems accessing our websites, only those with Windows 2000.

Is there a setting that I need to change that will allow my users Win2k computers to use the internal address of the website instead of the external address? If so where is that setting located?

Any additional tips or hints are appreciated.

Thanks,

Kevin

5 replies

by timwalsh

Is the internal domain name the same as the external domain name?

If so, make sure that your internal DNS zone has a CNAME (Alias)record that points the host name "www" to the internal IP address for the webserver.

If the domain names are different, create a HOST record for "www.externaldomain.com" and point it to the internal IP address.

by aaron_wurthmann

One, make sure your users are pointing at your new internal DNS server, I know that goes without saying.

Two, it sounds to me like your clients have cached the old info for your web server. On a Windows NT 4 client you can reboot to get rid of cached info. On Windows 2000 clients you can simply run " ipconfig /flushdns ". To get rid of cached info.

Please let us know if this helps, otherwise I have another idea for you.

This discussion is closed to new replies.