removing a dns record manually

  • Thread starter Thread starter Jaime
  • Start date Start date
J

Jaime

Okay.. we want to swap out a server that recently came off
of the lease and we would like to keep the same server
name. But when we shut down the old server we cannot move
the new server into the domain because it still "sees" the
old server with that name and a different IP. We've been
told that it could take up to 2 days for this to clear.
Since 2 days of down time for a server swap is not
acceptable I was wondering if there is a way to manually
clear this up.

Thank you for any help you can offer.

Jaime
 
Once you delete the DNS host record you need confirm that
it is removed from all DNS servers.
Rebooting the clients will obviously remove the cached
address. You could also try ipconfig /flushdns and
nbtstat -RR.
 
Didn't there used to be an issue with this and removing a dc from AD -
especially if you did not depromo the server first, but just unpluged it?
Something about you need to use one of the AD diag tools to manually go in
and remove some dc records from ad?
 
I think there was a bit of ambiguity in my question. When
I said we can't add the new server to the domain because
it still sees the old one, I meant that the domain still
sees the old one, not the new server. So, does the record
just have to be removed from our dns domain controller?

Jaime
 
Yes, however that would not affect the DNS records in any unique way.

If you have a DC that dies without a backup, you need to use ntdsutil to
clean up the metadata for that DC.
 
Yes I relized that and was what I was trying to project. The old one is (I
am guessing) still in AD by name and it is not allowing you to add it again.
As Michael said, you may need to use ntdsutil to remove the old DC before
you can add the new one.
 
Yes, however that would not affect the DNS records in any unique way.

Yes. I think this sounds more like he needs the ntdsutil method (as you
pointed out) and not a dns issue per se (from the dcpromo perspective.) I
don't believe the dns records would prevent him from adding that new DC,
however the old records in the AD schema gave me this problem before and the
ntdsutil cleared that up. Cheers!
--wjs
 
Back
Top