jbobst
asked on
Windows DNS Server - Reloaded a computer, and it is not aware of the new ip address
I have a Windows 2003 Domain controller running DNS. About a week ago, I formatted my computer's hard drive, reloaded Windows XP Pro, and re-attached it to the domain. I kept the same computer name after the Windows reload, and before I attached the "new" computer to the domain, I removed the old computer account in Active Directory. The problem is, the DNS server still thinks my computer has the old IP address. When I try to ping my computer now, or remote control it, the server or other computers on my network can't seem to locate it as they are looking for the old IP address.
Any ideas on how to fix this?
Thanks,
Jeff
Any ideas on how to fix this?
Thanks,
Jeff
ASKER
did that on another workstation (not the domain server) and it didn't work there. I'll try in on the server.
Also, make sure that your clients are using the DNS of your internal windows DNS server. Check the TCP/Ip settings..
All servers and workstations in your domain should be pointed only to the IP address of your windows DNS server. No computer should be pointed to the ISP DNS servers...
All servers and workstations in your domain should be pointed only to the IP address of your windows DNS server. No computer should be pointed to the ISP DNS servers...
ASKER
They are all pointing to the Widows DNS
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
With the exception of the NSLOOKUP, I have ping'd all the above...
Timed out on computername and computername.domain.local
Replied on the Real IP address.
Get back to you shortly on the NSLOOKUP
Timed out on computername and computername.domain.local
Replied on the Real IP address.
Get back to you shortly on the NSLOOKUP
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Seems to work now...(I did the ipconfig /registerdns and did a "clear cache" and "scavenge stale resouce records on the DNS server).
Thanks for the help.
By the way, this is probably a dump question, but what or how do I use NSLOOKUP???
I do have an AD integrated DNS...not sure if it's set to only allow secure updates or not...
Jeff
Thanks for the help.
By the way, this is probably a dump question, but what or how do I use NSLOOKUP???
I do have an AD integrated DNS...not sure if it's set to only allow secure updates or not...
Jeff
nslookup www.domain.com
thats it
thats it
NSLOOKUP is a builtin utilty that queries and tests DNS. You can run this on any client or server in your environment. Start --> RUN --> cmd <enter>
c:\NSLOOKUP <enter> <-- this will start the utility
In the utility, you can type names to query DNS...
domainname.local <enter> <--- this will give you the IP addresses of all your DC
server1 <enter> <-- This should return the IP address of Server1
192.168.3.55 <enter> <--- This will give you the name of the machine with the 192.168.3.55
all of this is querying DNS specifically....
c:\NSLOOKUP <enter> <-- this will start the utility
In the utility, you can type names to query DNS...
domainname.local <enter> <--- this will give you the IP addresses of all your DC
server1 <enter> <-- This should return the IP address of Server1
192.168.3.55 <enter> <--- This will give you the name of the machine with the 192.168.3.55
all of this is querying DNS specifically....
Go start run type cmd then type ipconfig /release then ipconfig renew
see if that helps