Windows NT 4.0 Domain, upgraded to Server 2003, now with DNS issues
Posted on 2003-12-01
First, the background. We were running a NT 4.0 Domain, with a Windows NT 4.0 Server machine as the Primary and only Domain Controller. Last week we upgraded the network to add a new Windows 2003 Server machine as the Domain Controller. To do this (because the old machine wasn't capable of coping with Window 2000 or better) I created a virtual machine running NT 4.0 Server as the Backup Domain Controller, promoted it to the Primary Domain Controller (and then removed the old machine), upgraded it to Windows 2000 Server, and after using adprep to prepare the network, added the new Windows 2003 Server to the network as a Domain Controller, and removed the virtual machine.
The problem we are having is that the new server (Bob - internal IP 10.1.1.167) is running DNS because it is the Domain Controller. However the gateway machine that connects the internal network to the outside world is a linux server, and previously we had all the machines that were allowed to connect to the internet with out ISP's DNS servers as their prefered and secondary DNS.
As far as I am aware, what we need to do is set all the machines in the office with Bob as their prefered and only DNS server, and then set Bob to forward anything it can't deal with (ie, anything not on the 10.1.1.* subnet) to the ISP's DNS server.
Am I right? If I am, how?
If I'm not, what am I supposed to be doing.
Information that might be relevant:
Internal Domain Name: DOMAIN
Internal DNS Domain Name: location.company.com.au
Internal DNS Server: 10.1.1.167
Internal gateway: 10.1.1.1
At the moment, we either have 10.1.1.167 as the prefered DNS server, and we seem to be able to browse inside the network easily, but can't get to any external web site, or we have the ISP's DNS servers as Prefered and secondary and can access external website, but we can't browse internally inside the network, and everything that involves network access is horendously slow.
Can anyone help?