DNS not scavenging old PTR record

[Eric Gardner]

I have added a new W2K Advanced server to our network, and gave it the same
name as an old server that has been long removed. I gave it a static IP
address and the address of our internal DNS server.

The problem is when I ping the new server by DNS name, it shows that it is
pinging the IP address of the old server. However, if I ping the IP address
of the new server I get a reply.

I went into the DNS and deleted the PTR records in the reverse lookup zone
for the old server, then manually added a PTR record for the new. Even after
restarting DNS I'm still getting the old IP address when I try to ping.

Any ideas why this new record isn't working, and why the stale record for my
old server wasn't deleted? And yes, I do have scavenging enabled for every 7
days. I have never checked to see how it was working, though.

Thanks.

 

[Kevin D. Goodknecht]

In

I have added a new W2K Advanced server to our network, and gave it
the same name as an old server that has been long removed. I gave it
a static IP address and the address of our internal DNS server.

The problem is when I ping the new server by DNS name, it shows that
it is pinging the IP address of the old server. However, if I ping
the IP address of the new server I get a reply.

I went into the DNS and deleted the PTR records in the reverse lookup
zone for the old server, then manually added a PTR record for the
new. Even after restarting DNS I'm still getting the old IP address
when I try to ping.

Any ideas why this new record isn't working, and why the stale record
for my old server wasn't deleted? And yes, I do have scavenging
enabled for every 7 days. I have never checked to see how it was
working, though.

Thanks.

The record for the old machine is probably still in the forward lookup zone,
and since the old machine owned the old record the new machine is unable to
update it.
The old record may not be time stamped and therefore becomes a persistent
record, delete the old record and run ipconfig /registerdns.

BTW, this is not a DC is it?
DCs cannot be simply turned off and removed from a domain, they must be
DCPROMOed out of the domain then DCPROMOed back in.

 

[Michael Johnston [MSFT]]

This is actually a forward lookup query. You need to change the record in the forward lookup zone to reflect the new IP address of the server. Make sure that
dynamic updates is enabled on the zone and the server in question is configured to dynamically register in DNS. This will prevent the record from becoming
stale or incorrect.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

 

[Eric Gardner]

I didn't see a record for it in the forward lookup zone, only in the reverse
lookup zone. The previous computer may have been a DC, but I don't think so.

If I put the nic team (it's a Compaq nic team) back to DHCP, then I am able
to get DNS resolution. In fact, I then changed the static IP address of the
team to the IP address of the previous server and was able to get
resolution. Wierd.