Disappearing/possibly corrupt A records

  • Thread starter Thread starter Bryan
  • Start date Start date
B

Bryan

My problem is this: We use DNS names in our printing
environment...in the initial setup of the printer, we
manually create an A record for the printer (and a PTR),
and then set it up. What has happened on too many
occasions now is that a printer will stop working, the
help desk will receive the call and notify me. I will
check the zone, and the A record will be gone. If I
recreate it, the printer starts to work! Running Windows
2000 SP4, DNS and DHCP from two servers (Standard, not AD
integrated), one has all primary zones, other has all
secondary zones.

Can anyone help?!?!?
 
The problem is likely because DHCP
is removing the DNS entry it at least
thinks it created. There are a couple of
other possibilities (I'd turn off scavenging
if you have it on to see if that helps.)

In theory at least, letting DHCP proxy-register
in DNS with what you've described should
be working fine. The record should come
and go as the lease is terminated and
renewed. So I'd also first make sure that
DDNS is enabled for the forward and
reverse zone and then boot the print
server and see what is actually going on.

One way around this that occurs to me is to set the
permissions on the A records you create to
disallow delete access by anyone.

To do this you have to decouple/copy
inheritance on the A record's rights, and
then edit the permissions on each holder
to disallow full access/delete.

I would think this should work (though I'm quite
willing to admit I've never tried it, not having
faced this problem before.) You may get
some harmless event log entries that might
even identify the culprit.

This may also make for a small maintenance
burden as the A record's owner will need to
reset the delete permission if you ever
decide you need to delete it. I don't see this
as any big deal.

Steve Duff, MCSE
Ergodic Systems, Inc.
 
Back
Top