I have inherited a Windows 2000 server that has lost DNS functionality for it's dhcp clients. According to the boss the Server and clients were working fine until the building power went out last week. I can browse the internet to my hearts content and do nslookups on outside internet addresses as long as I am on the server. However, I cannot do an nslookup on the internal addresses, unless I set the server via the nslookup command to the internal server address, then it works internally but not externally.
Rebooting the clients and running the ipconfig command confirms that the DHCP server is working and assigning the IP's, default route and dns information from the Scope options. However, if I go to a client and try IE it fails with a DNS error. If I try an nslookup from the client it fails with can't find name server non-existent host/domain.
From a DHCP client I can ping 10.0.0.1(internal interface), but I cannot ping 192.168.1.100 (outside interface). Routing problem? Or is this just normal funtionality.
Here is the configuration data:
Server: Windows 2000 with TWO NICs.
NIC -1 -Intenal Interface:
Default Gateway: None
Preferred DNS Servers:22.214.171.124, 126.96.36.199, 10.0.0.1
NIC -2 -External Interface:
IP Address:Assigned via DHCP from the ISP router. (usually 192.168.1.100, 101 etc)
Netmask:255.255.255.0 (assigned by router)
Default Gateway: 192.168.1.1 (assigned by router)
Preferred DNS Servers:188.8.131.52, 184.108.40.206 (assigned by router)
DHCP Address Range: 10.0.0.3-10.0.0.254
As best as I can tell the genius who set this up before me, set it up as a DNS root server with integrated AD.
I have read that because the system was setup as a DNS root server all I need to do is go in and DELETE the root (.) file folder and then setup DNS forwarding. My concern with this, is that once I delete the root (.) folder file I can't go back if things start going down hill (or can I?).
I have tried adding static routes between the two networks using the static route GUI and manually as follows: route add 192.168.1.0 10.0.0.1, route add 10.0.0.0 192.168.1.100
I called the ISP provider and asked them if they could provide me a static route on their router that points back to the 10.0.0.0 internal network. They laughed and said NO, that they also use the 10 address space and that would conflict with their networking.
I tried to configure NATon the internal ineterface, but it wants to use a 192.168.something addresses for NATing and DHCP. So I bagged that.
So, here I am at 3:00am trying to figure out what the heck to do and hoping one of you learned experts can help focus me on where the problem is.
V/R - Mark