• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 196
  • Last Modified:

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
0
jbobst
Asked:
jbobst
  • 4
  • 3
  • 2
  • +3
4 Solutions
 
davy999Commented:
Hi jbobst

Go start run type cmd then type ipconfig /release then ipconfig renew
see if that helps
0
 
jbobstAuthor Commented:
did that on another workstation (not the domain server) and it didn't work there.  I'll try in on the server.
0
 
NJComputerNetworksCommented:
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...

0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
jbobstAuthor Commented:
They are all pointing to the Widows DNS
0
 
NJComputerNetworksCommented:
Can you do a few tests from the domain controller:

POST results..


Ping problematiccomputername

Ping Problematiccomputername.domain.local

NSLOOKUP problematiccomputername

Ping -a xx.xx.xx.xx   (where xx.xx.xx.xx equals the REAL IP address of this problematic machine.)

thanks..
0
 
jbobstAuthor Commented:
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
0
 
mikeleebrlaCommented:
>>Timed out on computername and computername.domain.local
there lies your problem,, sounds as though the DNS server doesn't have an A record for this machine.

you can either manually create an A record for this machine on your DNS server

or

from the client, run ipconfig /registerdns to see if it will register that way
0
 
oBdACommented:
You probably have an AD integrated DNS, and set it to allow only secure updates; in this case, the new machine account doesn't have the permissions to change the entry. Open the DNS console, delete the old machine's host entry (and reverse lookup pointer, if present), open a command prompt on the new machine and enter "ipconfig /registerdns" (without the quotes).
0
 
bilbusCommented:
your dns server already has a entry for your pc, you need to delete the entry (your pc name) on the dns server. When done reboot your pc
0
 
jbobstAuthor Commented:
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
0
 
bilbusCommented:
nslookup www.domain.com 

thats it
0
 
NJComputerNetworksCommented:
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....



0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 4
  • 3
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now