usenet

Been doing some tidying of our 2003 R2 AD Integrated DNS to remove some
forward and reverse records that used upper case.

For the PTR records I deleted them using dnscmd.exe and they appear to
have gone and stayed gone.

The forward records, not all of which are upper case, when deleted
didn't re-appear after doing a refresh from the DNS MMC snap-in.

At this point I re-added them, all in lower case.

When I did a refresh from the MMC snap-in to check they had been
created, they had, but the cases exactly matched that of the "deleted"
records.

I guess it's being cached somewhere and isn't truly purged until either
some event, or for some period of time - my question is what is it?

All I want to do is delete RECORD1 and replace it with record1.

Thanks in advance (and sorry Microsoft but pathetic that I'm scrabbling
around with a command prompt because I dared to use the shift key
several years back when I created some records).

dusko savatovic

1. DNS names are not case sensitive, hence no need to change them
2. Your zones are probably set up to allow dynamic updates, which is correct
way to go. You are getting host records in your zones because, hosts
register their DNS names.
3. Writing manualy records that are dynamically registered is looking for
trouble. Manually entered records stay in the DNS base permanently, whereas
dynamic records update themselves as needed. Their names also have refresh
time to live. If they don't get refreshed during this time, they will be
removed from the DNS database at the next scvenging period.

ace fekay [microsoft certified trainer]

In news:usenet-23D4B5.20114922022009@eu.usenet-news.net,
Usenet <usenet@nospam.please>, posted the following:

In addition to Dusko's post, item #1, even though DNS is not case sensitive,
it will honor the registration request, that is if it is allowed, from the
host, and preserve the case of the record. If the hostname on the machine
itself is uppercase, the host record in DNS will be registered in uppercase.
You'll need to change the name on the host, but if they are DCs, that is not
so easy. I'm not even sure you can do it on a member server or client,
because if you try to change it using the same name but in lowercase, I
believe it may think nothing has changed and therefore stick with the
uppercase. Sorry, I don't have a machine available to test it. Give it a
shot, and let us know how you make out.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer
aceman@mvps.RemoveThisPart.org

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

usenet

Thanks for the reply - to clarify, these records are for devices we
manually registered, things like iLo cards etc. These days most things
Windows are left to register themselves, or DHCP does it, but we do have
old entries left to deal with.

I see with dynamically registered records the case is visible yet for
whatever reason they do appear to be purged when their age is exceeded,
looks like whatever the bug is it's only there in the GUI as dnscmd does
the job quite happily.

Odd thing is there's KB reference to a hotfix from years back, odd that
it doesn't seem to have made it into 2003 R2?

Cheers!