Dynamic Update not working

This is a Windows 2003 Domain and all servers are Windows 2003 with static IP
addresses. They can successfully complete the initial registration with DNS
but never update their time stamp so they are removed during scavenging. the
servers have the correct primary dns suffix which matches the DNS domain.
the correct DNS servers are listed in the IP configuration. the box to
register this connection's addresses in DNS is checked. the aging and
scavenging times are set to the defaults of 7 days for the No-refresh,
Refresh and scavenging period. the servers can be forced to re-register with
DNS with the ipconfig /registerdns command; but they do not update their
timestamps on their own. the registry key to disabledynamic updates is not
present. the servers all have the Write permission to their own record. our
production domain does mcafee turned on with the block IRC checked, but our
test domain does not have any anti-virus installed.

is there anything else i can check or do?

Is the DHCP Client service started? If it is not they will not update
records.

Chris

TPGBrennan wrote:
> This is a Windows 2003 Domain and all servers are Windows 2003 with static IP
> addresses. They can successfully complete the initial registration with DNS
> but never update their time stamp so they are removed during scavenging. the
> servers have the correct primary dns suffix which matches the DNS domain.
> the correct DNS servers are listed in the IP configuration. the box to
> register this connection's addresses in DNS is checked. the aging and
> scavenging times are set to the defaults of 7 days for the No-refresh,
> Refresh and scavenging period. the servers can be forced to re-register with
> DNS with the ipconfig /registerdns command; but they do not update their
> timestamps on their own. the registry key to disabledynamic updates is not
> present. the servers all have the Write permission to their own record. our
> production domain does mcafee turned on with the block IRC checked, but our
> test domain does not have any anti-virus installed.
>
> is there anything else i can check or do?
>

On Thu, 20 May 2010 16:50:01 -0700, TPGBrennan
<> wrote:

>This is a Windows 2003 Domain and all servers are Windows 2003 with static IP
>addresses. They can successfully complete the initial registration with DNS
>but never update their time stamp so they are removed during scavenging. the
>servers have the correct primary dns suffix which matches the DNS domain.
>the correct DNS servers are listed in the IP configuration. the box to
>register this connection's addresses in DNS is checked. the aging and
>scavenging times are set to the defaults of 7 days for the No-refresh,
>Refresh and scavenging period. the servers can be forced to re-register with
>DNS with the ipconfig /registerdns command; but they do not update their
>timestamps on their own. the registry key to disabledynamic updates is not
>present. the servers all have the Write permission to their own record. our
>production domain does mcafee turned on with the block IRC checked, but our
>test domain does not have any anti-virus installed.
>
>is there anything else i can check or do?

In addition to Chris' suggestion, are there any event log errors?

How many NICs are on the machine?


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.

The DHCP client service is running, there are no event log errors, most
servers have one NIC.

I got it working somewhat in my test domain. I deleted the A record and
forced a new dynamic registration as suggested in
http://blogs.technet.com/networkingâ...atient.​aspx.
The record was successully updated on the DNS server the client sent the
update to; however, the updated timestamp is not replicating between DCs. If
the client updates with one DC but another does the scavenging I'm still in
trouble.

"Ace Fekay [MVP - Directory Services, MCT" wrote:

> On Thu, 20 May 2010 16:50:01 -0700, TPGBrennan
> <> wrote:
>
> >This is a Windows 2003 Domain and all servers are Windows 2003 with static IP
> >addresses. They can successfully complete the initial registration with DNS
> >but never update their time stamp so they are removed during scavenging. the
> >servers have the correct primary dns suffix which matches the DNS domain.
> >the correct DNS servers are listed in the IP configuration. the box to
> >register this connection's addresses in DNS is checked. the aging and
> >scavenging times are set to the defaults of 7 days for the No-refresh,
> >Refresh and scavenging period. the servers can be forced to re-register with
> >DNS with the ipconfig /registerdns command; but they do not update their
> >timestamps on their own. the registry key to disabledynamic updates is not
> >present. the servers all have the Write permission to their own record. our
> >production domain does mcafee turned on with the block IRC checked, but our
> >test domain does not have any anti-virus installed.
> >
> >is there anything else i can check or do?
>
> In addition to Chris' suggestion, are there any event log errors?
>
> How many NICs are on the machine?
>
>
> 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.
> .
>

Re: failure to replicate timestamps.

That should only be the case if Aging is not enabled on the zone.
Otherwise it suggests a problem with replication since the timestamp is
part of the dnsRecord attribute.

Chris

TPGBrennan wrote:
> The DHCP client service is running, there are no event log errors, most
> servers have one NIC.
>
> I got it working somewhat in my test domain. I deleted the A record and
> forced a new dynamic registration as suggested in
> http://blogs.technet.com/networkingâ...atient.​aspx.
> The record was successully updated on the DNS server the client sent the
> update to; however, the updated timestamp is not replicating between DCs. If
> the client updates with one DC but another does the scavenging I'm still in
> trouble.
>
> "Ace Fekay [MVP - Directory Services, MCT" wrote:
>
>
>> On Thu, 20 May 2010 16:50:01 -0700, TPGBrennan
>> <> wrote:
>>
>>
>>> This is a Windows 2003 Domain and all servers are Windows 2003 with static IP
>>> addresses. They can successfully complete the initial registration with DNS
>>> but never update their time stamp so they are removed during scavenging. the
>>> servers have the correct primary dns suffix which matches the DNS domain.
>>> the correct DNS servers are listed in the IP configuration. the box to
>>> register this connection's addresses in DNS is checked. the aging and
>>> scavenging times are set to the defaults of 7 days for the No-refresh,
>>> Refresh and scavenging period. the servers can be forced to re-register with
>>> DNS with the ipconfig /registerdns command; but they do not update their
>>> timestamps on their own. the registry key to disabledynamic updates is not
>>> present. the servers all have the Write permission to their own record. our
>>> production domain does mcafee turned on with the block IRC checked, but our
>>> test domain does not have any anti-virus installed.
>>>
>>> is there anything else i can check or do?
>>>
>> In addition to Chris' suggestion, are there any event log errors?
>>
>> How many NICs are on the machine?
>>
>>
>> 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.
>> .
>>
>>

That is probably it; we have scavenging on in production but not in test. i
will turn it on and see if the timestamps get in sync.

"Chris Dent" wrote:

>
> Re: failure to replicate timestamps.
>
> That should only be the case if Aging is not enabled on the zone.
> Otherwise it suggests a problem with replication since the timestamp is
> part of the dnsRecord attribute.
>
> Chris
>
> TPGBrennan wrote:
> > The DHCP client service is running, there are no event log errors, most
> > servers have one NIC.
> >
> > I got it working somewhat in my test domain. I deleted the A record and
> > forced a new dynamic registration as suggested in
> > http://blogs.technet.com/networkingâ...atient.​aspx.
> > The record was successully updated on the DNS server the client sent the
> > update to; however, the updated timestamp is not replicating between DCs. If
> > the client updates with one DC but another does the scavenging I'm still in
> > trouble.
> >
> > "Ace Fekay [MVP - Directory Services, MCT" wrote:
> >
> >
> >> On Thu, 20 May 2010 16:50:01 -0700, TPGBrennan
> >> <> wrote:
> >>
> >>
> >>> This is a Windows 2003 Domain and all servers are Windows 2003 with static IP
> >>> addresses. They can successfully complete the initial registration with DNS
> >>> but never update their time stamp so they are removed during scavenging. the
> >>> servers have the correct primary dns suffix which matches the DNS domain.
> >>> the correct DNS servers are listed in the IP configuration. the box to
> >>> register this connection's addresses in DNS is checked. the aging and
> >>> scavenging times are set to the defaults of 7 days for the No-refresh,
> >>> Refresh and scavenging period. the servers can be forced to re-register with
> >>> DNS with the ipconfig /registerdns command; but they do not update their
> >>> timestamps on their own. the registry key to disabledynamic updates is not
> >>> present. the servers all have the Write permission to their own record. our
> >>> production domain does mcafee turned on with the block IRC checked, but our
> >>> test domain does not have any anti-virus installed.
> >>>
> >>> is there anything else i can check or do?
> >>>
> >> In addition to Chris' suggestion, are there any event log errors?
> >>
> >> How many NICs are on the machine?
> >>
> >>
> >> 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.
> >> .
> >>
> >>
> .
>

When I turned scavenging on the updated timestamps were successfully
replicated. It appears the final answer is to disable McAfee, delete the old
A record, and make sure scavenging is on.

"Chris Dent" wrote:

>
> Re: failure to replicate timestamps.
>
> That should only be the case if Aging is not enabled on the zone.
> Otherwise it suggests a problem with replication since the timestamp is
> part of the dnsRecord attribute.
>
> Chris
>
> TPGBrennan wrote:
> > The DHCP client service is running, there are no event log errors, most
> > servers have one NIC.
> >
> > I got it working somewhat in my test domain. I deleted the A record and
> > forced a new dynamic registration as suggested in
> > http://blogs.technet.com/networkingâ...atient.​aspx.
> > The record was successully updated on the DNS server the client sent the
> > update to; however, the updated timestamp is not replicating between DCs. If
> > the client updates with one DC but another does the scavenging I'm still in
> > trouble.
> >
> > "Ace Fekay [MVP - Directory Services, MCT" wrote:
> >
> >
> >> On Thu, 20 May 2010 16:50:01 -0700, TPGBrennan
> >> <> wrote:
> >>
> >>
> >>> This is a Windows 2003 Domain and all servers are Windows 2003 with static IP
> >>> addresses. They can successfully complete the initial registration with DNS
> >>> but never update their time stamp so they are removed during scavenging. the
> >>> servers have the correct primary dns suffix which matches the DNS domain.
> >>> the correct DNS servers are listed in the IP configuration. the box to
> >>> register this connection's addresses in DNS is checked. the aging and
> >>> scavenging times are set to the defaults of 7 days for the No-refresh,
> >>> Refresh and scavenging period. the servers can be forced to re-register with
> >>> DNS with the ipconfig /registerdns command; but they do not update their
> >>> timestamps on their own. the registry key to disabledynamic updates is not
> >>> present. the servers all have the Write permission to their own record. our
> >>> production domain does mcafee turned on with the block IRC checked, but our
> >>> test domain does not have any anti-virus installed.
> >>>
> >>> is there anything else i can check or do?
> >>>
> >> In addition to Chris' suggestion, are there any event log errors?
> >>
> >> How many NICs are on the machine?
> >>
> >>
> >> 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.
> >> .
> >>
> >>
> .
>

On Mon, 24 May 2010 12:58:01 -0700, TPGBrennan
<> wrote:

>When I turned scavenging on the updated timestamps were successfully
>replicated. It appears the final answer is to disable McAfee, delete the old
>A record, and make sure scavenging is on.
>

Disable McAfee? Did I miss something where this was mentioned earlier?

For any AV or installed security apps , I suggest and *highly*
recommend to exclude the NTDS and Sysvol folders. If you have
Exchange, exclude the whole Exchange folder and subfolders, as well as
the mailbox database/stores if located on another drive.

And I'm glad to hear that you have a handle on this now. :-)

Ace