Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Active Directory » DNS Server dot deleting old records
DNS Server dot deleting old records [message #334408] Thu, 03 December 2009 10:55 Go to next message
Nehemoth  is currently offline Nehemoth  Dominican Republic
Messages: 9
Registered: June 2009
Junior Member
First post here

I'm in a Domain in which we have two domain controllers and two DNS
servers (also WINS servers as Exchange 2003 was never fully tested
without it), also we are in native mode.

My problem is that we have an old bunch of records of all machines in
DNS, we have DHCP and the zone is configure for Dynamics update, so in
essence the old records should be delete it every 7 days cause
Scavenge is active.

I've search the web and I just found that the Scavenge should be
active in two places which we have but still the old records are
there.

I would like to know what can I do to eliminate this issue.

Note : I don't have any errors at my DNS Server Event Viewer.

Thank you
Re: DNS Server dot deleting old records [message #334421 is a reply to message #334408] Thu, 03 December 2009 11:06 Go to previous messageGo to next message
pbbergs  is currently offline pbbergs  United States
Messages: 1024
Registered: July 2009
Senior Member
Verify that you have "Advanced" turned on within your dns server console,
which is under View toolbar on top. Check to see if these A records have
the check box selected "Delete this record hwen it becomes stale".

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"Nehemoth" <nehemoth@gmail.com> wrote in message
news:33bb99b9-638c-457b-adc5-02ee4e0e674c@m25g2000yqc.googlegroups.com...
> First post here
>
> I'm in a Domain in which we have two domain controllers and two DNS
> servers (also WINS servers as Exchange 2003 was never fully tested
> without it), also we are in native mode.
>
> My problem is that we have an old bunch of records of all machines in
> DNS, we have DHCP and the zone is configure for Dynamics update, so in
> essence the old records should be delete it every 7 days cause
> Scavenge is active.
>
> I've search the web and I just found that the Scavenge should be
> active in two places which we have but still the old records are
> there.
>
> I would like to know what can I do to eliminate this issue.
>
> Note : I don't have any errors at my DNS Server Event Viewer.
>
> Thank you
Re: DNS Server dot deleting old records [message #334459 is a reply to message #334421] Thu, 03 December 2009 11:32 Go to previous messageGo to next message
Nehemoth  is currently offline Nehemoth  Dominican Republic
Messages: 9
Registered: June 2009
Junior Member
Yes, those records are checked for deletion after stale state


On Dec 3, 2:06 pm, "Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com>
wrote:
> Verify that you have "Advanced" turned on within your dns server console,
> which is under View toolbar on top.  Check to see if these A records have
> the check box selected "Delete this record hwen it becomes stale".
>
> --
> Paul Bergson
> MVP - Directory Services
> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
> Microsoft's Thrive IT Pro of the Month - June 2009
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup This
> posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Nehemoth" <nehem...@gmail.com> wrote in message
>
> news:33bb99b9-638c-457b-adc5-02ee4e0e674c@m25g2000yqc.googlegroups.com...
>
> > First post here
>
> > I'm in a Domain in which we have two domain controllers and two DNS
> > servers (also WINS servers as Exchange 2003 was never fully tested
> > without it), also we are in native mode.
>
> > My problem is that we have an old bunch of records of all machines in
> > DNS, we have DHCP and the zone is configure for Dynamics update, so in
> > essence the old records should be delete it every 7 days cause
> > Scavenge is active.
>
> > I've search the web and I just found that the Scavenge should be
> > active in two places which we have but still the old records are
> > there.
>
> > I would like to know what can I do to eliminate this issue.
>
> > Note : I don't have any errors at my DNS Server Event Viewer.
>
> > Thank you
Re: DNS Server dot deleting old records [message #334769 is a reply to message #334459] Thu, 03 December 2009 17:45 Go to previous messageGo to next message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Nehemoth" <nehemoth@gmail.com> wrote in message
news:1a79f61d-86c2-4807-8c42-02dd56eeb3fc@z41g2000yqz.googlegroups.com...
>
> Yes, those records are checked for
> deletion after stale state
>

Scavenging alone will not delete old records or duplicates. Have you either
configured credentials for DHCP to use when registering records, or assuming
DHCP is on a DC, added the DHCP server to the DnsProxyUpdate group? Either
action in conjunction with *forcing* DHCP (DHCP properties, update all
records whether the client requests it or not), will make DHCP own the
record so it can update it, otherwise, DHCP can't update a record it does
not own. This is because by default. You may have to delete current
duplicate records until it gets caught up.

Read up on it in the following blog, please.

DHCP, Dynamic DNS Updates, Scavenging, static entries & timestamps, and the
DnsProxyUpdate Group (How to remove duplicate DNS host records)
http://msmvps.com/blogs/acefekay/archive/2009/08/20/dhcp-dyn amic-dns-updates-scavenging-static-entries-amp-timestamps-an d-the-dnsproxyupdate-group.aspx


--
Ace

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

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Re: DNS Server dot deleting old records [message #335054 is a reply to message #334769] Fri, 04 December 2009 05:43 Go to previous messageGo to next message
Nehemoth  is currently offline Nehemoth  Dominican Republic
Messages: 9
Registered: June 2009
Junior Member
Thank you ofor the answer, Let me read a little bit.


On Dec 3, 8:45 pm, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
wrote:
> "Nehemoth" <nehem...@gmail.com> wrote in message
>
> news:1a79f61d-86c2-4807-8c42-02dd56eeb3fc@z41g2000yqz.googlegroups.com...
>
>
>
> > Yes, those records are checked for
> > deletion after stale state
>
> Scavenging alone will not delete old records or duplicates. Have you either
> configured credentials for DHCP to use when registering records, or assuming
> DHCP is on a DC, added the DHCP server to the DnsProxyUpdate group? Either
> action in conjunction with *forcing* DHCP (DHCP properties, update all
> records whether the client requests it or not), will make DHCP own the
> record so it can update it, otherwise, DHCP can't update a record it does
> not own. This is because by default. You may have to delete current
> duplicate records until it gets caught up.
>
> Read up on it in the following blog, please.
>
> DHCP, Dynamic DNS Updates, Scavenging, static entries & timestamps, and the
> DnsProxyUpdate Group (How to remove duplicate DNS host records) http://msmvps.com/blogs/acefekay/archive/2009/08/20/dhcp-dyn amic-dns-...
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit among
> responding engineers, and to help others benefit from your resolution.
>
> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
> 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please checkhttp://support.microsoft.comfor regional support phone numbers.
Re: DNS Server dot deleting old records [message #335062 is a reply to message #335054] Fri, 04 December 2009 05:52 Go to previous messageGo to next message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Nehemoth" <nehemoth@gmail.com> wrote in message
news:ad0bb24e-9b2a-47be-be10-792d066d8fac@e27g2000yqd.googlegroups.com...
Thank you ofor the answer, Let me read a little bit.


On Dec 3, 8:45 pm, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
wrote:
> "Nehemoth" <nehem...@gmail.com> wrote in message
>
> news:1a79f61d-86c2-4807-8c42-02dd56eeb3fc@z41g2000yqz.googlegroups.com...
>
>
>
> > Yes, those records are checked for
> > deletion after stale state
>
> Scavenging alone will not delete old records or duplicates. Have you
> either
> configured credentials for DHCP to use when registering records, or
> assuming
> DHCP is on a DC, added the DHCP server to the DnsProxyUpdate group? Either
> action in conjunction with *forcing* DHCP (DHCP properties, update all
> records whether the client requests it or not), will make DHCP own the
> record so it can update it, otherwise, DHCP can't update a record it does
> not own. This is because by default. You may have to delete current
> duplicate records until it gets caught up.
>
> Read up on it in the following blog, please.
>
> DHCP, Dynamic DNS Updates, Scavenging, static entries & timestamps, and
> the
> DnsProxyUpdate Group (How to remove duplicate DNS host
> records) http://msmvps.com/blogs/acefekay/archive/2009/08/20/dhcp-dyn amic-dns-...
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among
> responding engineers, and to help others benefit from your resolution.
>
> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
> 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please
> checkhttp://support.microsoft.comfor regional support phone numbers.



You are welcome!

Ace
Re: DNS Server dot deleting old records [message #335074 is a reply to message #334769] Fri, 04 December 2009 06:26 Go to previous messageGo to next message
pbbergs  is currently offline pbbergs  United States
Messages: 1024
Registered: July 2009
Senior Member
Good point Ace. I didn't even think of pointing that out.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"Ace Fekay [MCT]" <aceman@mvps.RemoveThisPart.org> wrote in message
news:uHalOsHdKHA.4780@TK2MSFTNGP04.phx.gbl...
> "Nehemoth" <nehemoth@gmail.com> wrote in message
> news:1a79f61d-86c2-4807-8c42-02dd56eeb3fc@z41g2000yqz.googlegroups.com...
>>
>> Yes, those records are checked for
>> deletion after stale state
>>
>
> Scavenging alone will not delete old records or duplicates. Have you
> either configured credentials for DHCP to use when registering records, or
> assuming DHCP is on a DC, added the DHCP server to the DnsProxyUpdate
> group? Either action in conjunction with *forcing* DHCP (DHCP properties,
> update all records whether the client requests it or not), will make DHCP
> own the record so it can update it, otherwise, DHCP can't update a record
> it does not own. This is because by default. You may have to delete
> current duplicate records until it gets caught up.
>
> Read up on it in the following blog, please.
>
> DHCP, Dynamic DNS Updates, Scavenging, static entries & timestamps, and
> the DnsProxyUpdate Group (How to remove duplicate DNS host records)
> http://msmvps.com/blogs/acefekay/archive/2009/08/20/dhcp-dyn amic-dns-updates-scavenging-static-entries-amp-timestamps-an d-the-dnsproxyupdate-group.aspx
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
> 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>
>
>
Re: DNS Server dot deleting old records [message #335193 is a reply to message #335074] Fri, 04 December 2009 09:19 Go to previous messageGo to next message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com> wrote in message
news:eK3mtVOdKHA.4724@TK2MSFTNGP05.phx.gbl...
> Good point Ace. I didn't even think of pointing that out.
>

I know you knew that, too! Just may have forgot. :-)
Re: DNS Server dot deleting old records [message #379836 is a reply to message #334769] Fri, 29 January 2010 07:01 Go to previous messageGo to next message
Nehemoth  is currently offline Nehemoth  Dominican Republic
Messages: 9
Registered: June 2009
Junior Member
On Dec 3 2009, 8:45 pm, "Ace Fekay [MCT]"
<ace...@mvps.RemoveThisPart.org> wrote:
> "Nehemoth" <nehem...@gmail.com> wrote in message
>
> news:1a79f61d-86c2-4807-8c42-02dd56eeb3fc@z41g2000yqz.googlegroups.com...
>
>
>
> > Yes, thoserecordsare checked for
> > deletion after stale state
>
> Scavenging alone will not deleteoldrecordsor duplicates. Have you either
> configured credentials for DHCP to use when registeringrecords, or assuming
> DHCP is on a DC, added the DHCPserverto the DnsProxyUpdate group? Either
> action in conjunction with *forcing* DHCP (DHCP properties, update allrecordswhether the client requests it or not), will make DHCP own the
> record so it can update it, otherwise, DHCP can't update a record it does
> not own. This is because by default. You may have to delete current
> duplicaterecordsuntil it gets caught up.
>
> Read up on it in the following blog, please.
>
> DHCP, DynamicDNSUpdates, Scavenging, static entries & timestamps, and the
> DnsProxyUpdate Group (How to remove duplicateDNShostrecords) http://msmvps..com/blogs/acefekay/archive/2009/08/20/dhcp-dy namic-dns-...
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit among
> responding engineers, and to help others benefit from your resolution.
>
> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
> 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please checkhttp://support.microsoft.comfor regional support phone numbers.

Hello

Let me thank you for the guide.

I'm trying to take advantage of this information.

But there something that I don't understand in the guide so I need
some clarification.

First I need to tell you that as I have my DHCP in another server
different than our DNS/Domain Controller I will Choose the option one,
so I should follow the below instructions as per article
Option 1:

1. Add the DHCP server to the DnsUpdateProxy Group.
2. Force DHCP to register all records, Forward and PTR, (whether a
client machine can do it or not) in the Option 081 tab (DHCP
properties, DNS tab).
3. Set Option 015 to the AD domain name (such as example.com).
4. Set Option 006 to only the internal DNS servers.
5. If the zone is set for Secure Updates Only, then DHCP cannot
update non-Microsoft clients and Microsoft clients that are not joined
to the domain. In this case, you will need to create and configure a
user account for use as credentials for DHCP to register such clients.

My problem is with the number 2 (Force DHCP to register all records,
Forward and PTR, (whether a client machine can do it or not) in the
Option 081 tab (DHCP properties, DNS tab). The Force DHCP to register
all records, Forward and PTR, is the one you get in the DHCP server
properties > DNS TAB > Always Dynamically Update DNS A and PTR records
but I get lost when talk about the option 081 tab, so what is that?

I even check in the Predefined Options and Values there isn't a 081
option.

Please somebody can help me here?

Thank you
Re: DNS Server dot deleting old records [message #379906 is a reply to message #379836] Fri, 29 January 2010 08:15 Go to previous message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
> On Dec 3 2009, 8:45 pm, "Ace Fekay [MCT]"
> <ace...@mvps.RemoveThisPart.org> wrote:
>> "Nehemoth" <nehem...@gmail.com> wrote in message
>>
>> news:1a79f61d-86c2-4807-8c42-02dd56eeb3fc@z41g2000yqz.googlegroups.com...
>>
>>
>>
>>> Yes, thoserecordsare checked for
>>> deletion after stale state
>>
>> Scavenging alone will not deleteoldrecordsor duplicates. Have you either
>> configured credentials for DHCP to use when registeringrecords, or assuming
>> DHCP is on a DC, added the DHCPserverto the DnsProxyUpdate group? Either
>> action in conjunction with *forcing* DHCP (DHCP properties, update
>> allrecordswhether the client requests it or not), will make DHCP own the
>> record so it can update it, otherwise, DHCP can't update a record it does
>> not own. This is because by default. You may have to delete current
>> duplicaterecordsuntil it gets caught up.
>>
>> Read up on it in the following blog, please.
>>
>> DHCP, DynamicDNSUpdates, Scavenging, static entries & timestamps, and the
>> DnsProxyUpdate Group (How to remove
>> duplicateDNShostrecords) http://msmvps.com/blogs/acefekay/archive/2009/08/20/dhcp-dyn amic-dns-...
>>
>> --
>> Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.
>>
>> Please reply back to the newsgroup or forum for collaboration benefit among
>> responding engineers, and to help others benefit from your resolution.
>>
>> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
>> 2003/2000, MCSA Messaging 2003
>> Microsoft Certified Trainer
>>
>> For urgent issues, please contact Microsoft PSS directly. Please
>> checkhttp://support.microsoft.comfor regional support phone numbers.
>
> Hello
>
> Let me thank you for the guide.
>
> I'm trying to take advantage of this information.
>
> But there something that I don't understand in the guide so I need
> some clarification.
>
> First I need to tell you that as I have my DHCP in another server
> different than our DNS/Domain Controller I will Choose the option one,
> so I should follow the below instructions as per article
> Option 1:
>
> 1. Add the DHCP server to the DnsUpdateProxy Group.
> 2. Force DHCP to register all records, Forward and PTR, (whether a
> client machine can do it or not) in the Option 081 tab (DHCP
> properties, DNS tab).
> 3. Set Option 015 to the AD domain name (such as example.com).
> 4. Set Option 006 to only the internal DNS servers.
> 5. If the zone is set for Secure Updates Only, then DHCP cannot
> update non-Microsoft clients and Microsoft clients that are not joined
> to the domain. In this case, you will need to create and configure a
> user account for use as credentials for DHCP to register such clients.
>
> My problem is with the number 2 (Force DHCP to register all records,
> Forward and PTR, (whether a client machine can do it or not) in the
> Option 081 tab (DHCP properties, DNS tab). The Force DHCP to register
> all records, Forward and PTR, is the one you get in the DHCP server
> properties > DNS TAB > Always Dynamically Update DNS A and PTR records
> but I get lost when talk about the option 081 tab, so what is that?
>
> I even check in the Predefined Options and Values there isn't a 081
> option.
>
> Please somebody can help me here?
>
> Thank you


Hello Nehomoth,

I thought you had resolved this by now. Your last post was on 12/4 last
year.

Actually, Option 081 is the DNS tab in DHCP properties. You will not
find it as a Server or Scope Option. Option 081 defines DNS Dynamic
Updates.

If DHCP is on a non-domain controller, go with the credentials method.
If DHCP is on a domain controller, go with either the credentials
method or the DnsProxyUpdate group method.

--
Ace

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

Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE
& MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance,
please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Previous Topic:Authentification on Win2k8 r2 inter site
Next Topic:Store connection strings/configuration settings in A/D
Goto Forum:
  


Current Time: Tue Jan 16 10:39:19 MST 2018

Total time taken to generate the page: 0.07050 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software