Duplicate PTR records in reverse lookup zone

[TSAM]

Hello,

We run Windows 2003 domain with AD integrated DNS. We run DHCP server for
our clients.

We get duplicate entries for dynamic updated clients in the reverse lookup
zone. Our DHCP server settings is as follows:

1. Enable DNS dynamic updates according to the settings below:
2. Always dynamically update DNS A and PTR reecords
3.Discard A and PTR records when lease is deleted
4.Dynamically update DNS A and PTR records for DHCP clients ..... NT4.0
.....

Our forward lookup zones don't have any duplicates. How could I avoid
duplicate PTR records in our reverse lookup zone for DHCP subnet.

TIA

[Meinolf Weber]

Hello TSAM,

Check out this one for updating DNS:
http://technet.microsoft.com/en-us/l.../cc787034.aspx

Or you can also configure aging/scavenging on the zone properties general
tab.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hello,
>
> We run Windows 2003 domain with AD integrated DNS. We run DHCP server
> for our clients.
>
> We get duplicate entries for dynamic updated clients in the reverse
> lookup zone. Our DHCP server settings is as follows:
>
> 1. Enable DNS dynamic updates according to the settings below:
> 2. Always dynamically update DNS A and PTR reecords
> 3.Discard A and PTR records when lease is deleted
> 4.Dynamically update DNS A and PTR records for DHCP clients .....
> NT4.0
> ....
> Our forward lookup zones don't have any duplicates. How could I avoid
> duplicate PTR records in our reverse lookup zone for DHCP subnet.
>
> TIA
>

[TSAM]

Thanks.

I never been a fan nor I trusted scavenging to be honest. But why are we
seeing duplicate PTR's in reverse lookup zone and how to eliminate this
without using scavenging?

TIA

"Meinolf Weber" wrote:

> Hello TSAM,
>
> Check out this one for updating DNS:
> http://technet.microsoft.com/en-us/l.../cc787034.aspx
>
> Or you can also configure aging/scavenging on the zone properties general
> tab.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Hello,
> >
> > We run Windows 2003 domain with AD integrated DNS. We run DHCP server
> > for our clients.
> >
> > We get duplicate entries for dynamic updated clients in the reverse
> > lookup zone. Our DHCP server settings is as follows:
> >
> > 1. Enable DNS dynamic updates according to the settings below:
> > 2. Always dynamically update DNS A and PTR reecords
> > 3.Discard A and PTR records when lease is deleted
> > 4.Dynamically update DNS A and PTR records for DHCP clients .....
> > NT4.0
> > ....
> > Our forward lookup zones don't have any duplicates. How could I avoid
> > duplicate PTR records in our reverse lookup zone for DHCP subnet.
> >
> > TIA
> >
>
>
>

[Meinolf Weber]

Hello TSAM,

If a user press power off button the client can not correctly unregister
itself for example.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Thanks.
>
> I never been a fan nor I trusted scavenging to be honest. But why are
> we seeing duplicate PTR's in reverse lookup zone and how to eliminate
> this without using scavenging?
>
> TIA
>
> "Meinolf Weber" wrote:
>
>> Hello TSAM,
>>
>> Check out this one for updating DNS:
>> http://technet.microsoft.com/en-us/l.../cc787034.aspx
>> Or you can also configure aging/scavenging on the zone properties
>> general tab.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Hello,
>>>
>>> We run Windows 2003 domain with AD integrated DNS. We run DHCP
>>> server for our clients.
>>>
>>> We get duplicate entries for dynamic updated clients in the reverse
>>> lookup zone. Our DHCP server settings is as follows:
>>>
>>> 1. Enable DNS dynamic updates according to the settings below:
>>> 2. Always dynamically update DNS A and PTR reecords
>>> 3.Discard A and PTR records when lease is deleted
>>> 4.Dynamically update DNS A and PTR records for DHCP clients .....
>>> NT4.0
>>> ....
>>> Our forward lookup zones don't have any duplicates. How could I
>>> avoid
>>> duplicate PTR records in our reverse lookup zone for DHCP subnet.
>>> TIA
>>>

[A, Deji]

Well, you better start loving scavenging because it is designed to do
exactly what you are looking to do.

Deji
"TSAM" <TSAM@discussions.microsoft.com> wrote in message
news:A7A3B918-46AF-43D7-B13F-E1A3418A4FE0@microsoft.com...
> Thanks.
>
> I never been a fan nor I trusted scavenging to be honest. But why are we
> seeing duplicate PTR's in reverse lookup zone and how to eliminate this
> without using scavenging?
>
> TIA
>
> "Meinolf Weber" wrote:
>
>> Hello TSAM,
>>
>> Check out this one for updating DNS:
>> http://technet.microsoft.com/en-us/l.../cc787034.aspx
>>
>> Or you can also configure aging/scavenging on the zone properties general
>> tab.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>
>>
>> > Hello,
>> >
>> > We run Windows 2003 domain with AD integrated DNS. We run DHCP server
>> > for our clients.
>> >
>> > We get duplicate entries for dynamic updated clients in the reverse
>> > lookup zone. Our DHCP server settings is as follows:
>> >
>> > 1. Enable DNS dynamic updates according to the settings below:
>> > 2. Always dynamically update DNS A and PTR reecords
>> > 3.Discard A and PTR records when lease is deleted
>> > 4.Dynamically update DNS A and PTR records for DHCP clients .....
>> > NT4.0
>> > ....
>> > Our forward lookup zones don't have any duplicates. How could I avoid
>> > duplicate PTR records in our reverse lookup zone for DHCP subnet.
>> >
>> > TIA
>> >
>>
>>
>>