Issues with DNS on a Windows 2000 domain
Hello Experts,
I am having some DNS issues that I am hoping you can help me with. Here is some background information that may be useful.
1. I have two DNS servers on the network: DC1 (primary DNS server) and DC2 (secondary DNS server). These servers are configured as follows:
• DC1 – IP address = 172.16.1.23
• DC2 – IP address = 172.16.1.15
2. I have just replaced a department’s workstations. The new workstations are running XP Pro with the latest updates and the old workstations were running a combination of Windows 2000 Professional and XP Pro. All of the work stations have static IP addresses (this is a requirement) and are configured as follows:
Workstation name: AP-WSX (X is the computer number. Valid names in the department would be AP-WS1, AP-WS2, etc…)
IP address = 10.37.21.x All IP addresses are statically assigned
Subnet mask = 255.255.255.0
Gateway = 10.37.21.1
Primary DNS = 172.16.1.23
Secondary DNS = 172.16.1.15
There is no WINS on the network.
All of the workstations have been joined to the domain, and all can access the network resources that they need to access. The problem I am running into is I cannot access any of the new resources via our remote administration program. I try pinging the addresses and I get no reply. When I do a trace route, DNS does not resolve the IP address to the correct computer name. It resolves it to the old computer name. So if a user had a computer named AP-WSA with an IP of 10.37.21.115 and we replaced that computer with AP-WS1, my trace route is still trying to connect to AP-WSA.
I have gone into DNS administrator on both DC1 and in the forward lookup zone, I see an entry for AP-WSA with an IP of 10.37.21.115 and an entry for AP-WS1 with an IP of 10.37.21.115. When I go into the reverse lookup zone, all I see is an entry for AP-WSA with an IP 10.37.21.115.
My questions are:
1. Shouldn’t the new computers registered themselves with correct information in DNS by now? The new computers were put online early last week.
2. Is there a way to force these computers to reregister their DNS information?
3. When I ping or do a trace route to a computer, is the forward lookup zone or the reverse lookup zone to resolve?
4. DNS is obviously something that I have not had much experience with, but it appears (since the tech that used to manage DNS has moved on) that I will be doing more DNS administration, so do you know of some good resources that I can get to bring myself up to speed?
Any help or suggestions would be greatly appreciated.
Regards,
Nick
I am having some DNS issues that I am hoping you can help me with. Here is some background information that may be useful.
1. I have two DNS servers on the network: DC1 (primary DNS server) and DC2 (secondary DNS server). These servers are configured as follows:
• DC1 – IP address = 172.16.1.23
• DC2 – IP address = 172.16.1.15
2. I have just replaced a department’s workstations. The new workstations are running XP Pro with the latest updates and the old workstations were running a combination of Windows 2000 Professional and XP Pro. All of the work stations have static IP addresses (this is a requirement) and are configured as follows:
Workstation name: AP-WSX (X is the computer number. Valid names in the department would be AP-WS1, AP-WS2, etc…)
IP address = 10.37.21.x All IP addresses are statically assigned
Subnet mask = 255.255.255.0
Gateway = 10.37.21.1
Primary DNS = 172.16.1.23
Secondary DNS = 172.16.1.15
There is no WINS on the network.
All of the workstations have been joined to the domain, and all can access the network resources that they need to access. The problem I am running into is I cannot access any of the new resources via our remote administration program. I try pinging the addresses and I get no reply. When I do a trace route, DNS does not resolve the IP address to the correct computer name. It resolves it to the old computer name. So if a user had a computer named AP-WSA with an IP of 10.37.21.115 and we replaced that computer with AP-WS1, my trace route is still trying to connect to AP-WSA.
I have gone into DNS administrator on both DC1 and in the forward lookup zone, I see an entry for AP-WSA with an IP of 10.37.21.115 and an entry for AP-WS1 with an IP of 10.37.21.115. When I go into the reverse lookup zone, all I see is an entry for AP-WSA with an IP 10.37.21.115.
My questions are:
1. Shouldn’t the new computers registered themselves with correct information in DNS by now? The new computers were put online early last week.
2. Is there a way to force these computers to reregister their DNS information?
3. When I ping or do a trace route to a computer, is the forward lookup zone or the reverse lookup zone to resolve?
4. DNS is obviously something that I have not had much experience with, but it appears (since the tech that used to manage DNS has moved on) that I will be doing more DNS administration, so do you know of some good resources that I can get to bring myself up to speed?
Any help or suggestions would be greatly appreciated.
Regards,
Nick
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.