Re: Reverse Lookup (PTR Record) Problem

If this is lab environment, you can change TTL on the records in reverse
lookup zone temporarily, to keep it clean. Do you have any application or
process that can actually benefit form reverse look-up queries?

Toni

"admcse" <admcse@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:71201797-0AEF-4A91-90E4-4FC03428A094@xxxxxxxxxxxxxxxx
OK, I'll give that a try.

My only concern is that this happens over a short period of time, less
than
one day. This is a test lab (which will eventually be moved into
production)
so I image around 200 machines overnight so in the morning they all have
two
PTR entries, one for the imaging phase and the correct on with the
computername once it boots to the OS.

Is it advisable to have such a short TTL on the records in this zone and
is
there any adverse effects from having a different scavenging time on the
reverse and forward zones?

Let me know.

Thanks
Angelo
"T. Uranjek" wrote:

Hi!

You should enable scavenging for reverse look up zone and the in the
properties of this zone on Advanced tab select Enable automatic
scavenging .

More info:
http://technet2.microsoft.com/WindowsServer/en/library/20fbbd82-0cea-4a74-9634-fdd993f4c4f41033.mspx?mfr=true

Toni


"admcse" <admcse@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A99F2481-E77A-459C-B74E-99DF822CC5DB@xxxxxxxxxxxxxxxx
Hello,

Can someone please help me with a problem I am having with DNS Reverse
Lookup (PTR) records being updated/deleted correctly. The is causing
our
in-house application (which relies heavily on rlookup) major problems.

PROBLEM
PTR records are not being updated/removed correctly. This is causing
there
to be multiple machines to have the same IP address in the Reverse
Lookup
zone.

What I noticed is that all the machines with stale PTR records all got
thier
IP during the imaging process (SMS OSD) but the PTR records were not
deleted
after the imaging process was completed. There was like 20 entries for
3
different imaged computers.

See below for our environment info.

Thanks
Angelo


ENVIRONMENT

All Servers are Windows 2003 Std with SP1
All Clients are XP with SP2

I have DNS running on my 2 AD servers
AD Integrated
Secure Updates only
Aging - set to 7 days

DHCP is running in a different server and is set to the following:
Always dynamically update DNS A and PTR records
Discard A and PTR records when lease is deleted
Dynamically update DNS A and PTR records for DHCP clients that do not
request udpates





.

Relevant Pages

  • Re: Reverse Lookup (PTR Record) Problem
    ... properties of this zone on Advanced tab select Enable automatic scavenging. ... Can someone please help me with a problem I am having with DNS Reverse ... PTR records are not being updated/removed correctly. ... Dynamically update DNS A and PTR records for DHCP clients that do not ...
    (microsoft.public.windows.server.dns)
  • Re: Cannot find domain controller
    ... If the Reverse lookup zone was created make sure that allows dynamic ... Remember that reverse zones are not automagically created. ... the registration of PTR records because you can work fine without ... I wouldn't go by disabling reverse registration as the article suggests. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Reverse Lookup (PTR Record) Problem
    ... Is it advisable to have such a short TTL on the records in this zone and is ... You should enable scavenging for reverse look up zone and the in the ... PTR records are not being updated/removed correctly. ... Dynamically update DNS A and PTR records for DHCP clients that do not ...
    (microsoft.public.windows.server.dns)
  • RE: Domain Upgrade Documentation
    ... and then click the DNS tab. ... > the forward zone on DNS server and recreate on AD-intergrated zone. ... > on the reverse zone, instead of the both an A and PTR records. ...
    (microsoft.public.windows.server.migration)
  • Re: Cannot find domain controller
    ... But again, last time I saw this errors, the solution was to create a Reverse ... I under if the Reverse Zone that the poster created was allowing Dynamic ... AD DNS progressive.local ... use PTR records, you'll see you can live without them. ...
    (microsoft.public.windows.server.active_directory)