Two W2k server hosthames resolving to the same IP address

[quentinhudson]

Hi,

We run a Windows 2000 network with DNS and have one WINS server for
legacy clients.
I built a new server (DC5) with the IP address 172.16.0.47 which I was
given by my boss, with the intention of making it a DC. Unfortunately,
I had to scrap it a few days later as it was a Windows 2003 box, and
after consultation I came to the conclusion that the new DC should be a
Windows 2000 box like all the others. I deleted the object from AD, and
tombstoned it in WINS, and built a new server (DC6) using the same IP
address. Unfortunately, now it is several weeks later and if you ping
DC5 or DC6 they both resolve to the same IP adddress. If you run an
nslookup on the IP address it chooses the correct server. I had a look
in DNS and did not see it in there - although I am no expert in this
area. Obviously, somewhere in AD there is a reference to the defunct
DC5, but I dont know where. I would like to get rid of this record and
resolve this problem. Any suggestions gratefully received.

Kind regards,

QH

 

[Richard G. Harper]

Did you check WINS to be sure the record has been purged? How about DHCP?
Did you purge the cache on the DNS server and on the local computer prior to
pinging the old name?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[quentinhudson]

Thanks for the advice, however please bear with me as I am not very
knowledgeable about such things.

I went into WINS, right-clickec on Active Registrations, chose "Find by
name" and typed in the name of the box that was killed (DC5). There
were no results, although incidentally there were also none for its
replacement (DC6) either.

I did not check DHCP before as the server had a statically configured
IP address configured within Network Settings. I just had a look a
moment ago however, and I did not see the 172.16.0.47 address there,
which is what I expected.

As for purging the DNS cache, do you mean IPCONFG /FLUSHDNS? I have
done that, but DC5 still ping to the 172.16.0.47 despite the fact it
does not exist.

Any ideas welcome.

QH

 

[Kevin D. Goodknecht Sr. [MVP]]

Thanks for the advice, however please bear with me as I am not very
knowledgeable about such things.

I went into WINS, right-clickec on Active Registrations, chose "Find
by name" and typed in the name of the box that was killed (DC5). There
were no results, although incidentally there were also none for its
replacement (DC6) either.

I did not check DHCP before as the server had a statically configured
IP address configured within Network Settings. I just had a look a
moment ago however, and I did not see the 172.16.0.47 address there,
which is what I expected.

As for purging the DNS cache, do you mean IPCONFG /FLUSHDNS? I have
done that, but DC5 still ping to the 172.16.0.47 despite the fact it
does not exist.

In your original post you said you used the same IP on DC6.
When you use ping are you pinging the IP address or the host name?
If you're ping the IP address, look in the reverse lookup zone for the PTR.
If you are pinging the host name, the record would have to be in the Forward
lookup zone or in WINS.

 

[quentinhudson]

Thanks a lot for that, it was in the forward zone. I thought I had
deleted the record before, but evidently not.

Cheers,

QH