DNS server has updated its own host (A) records. In order to ensure that
its DS-integrated peer DNS servers are able to replicate with this server,
an attempt was made to update them with the new records through dynamic
update. An error was encountered during this update, the record data is the
error code.

If this DNS server does not have any DS-integrated peers, then this error
should be ignored.

If this DNS server's Active Directory replication partners do not have the
correct IP address(es) for this server, they will be unable to replicate
with it.

To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS
server.
2) Open DnsManager and connect in turn to each of the replication partners.

i using win2003 and exchange 2003 , after i drpromo another win2003 to DC ,
then show these error message

Hi

Are your Dns Zones AD integrated?
Is this new server going to be a Dns Server?
Is this server an aditional server for the same domain or did you created a
new domain?
Is in same subnet?
Can you post the results for ipconfig /all


--
I hop that helps

Good Luck
Jorge Silva
MCSA
Systems Administrator





"Tequila" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> DNS server has updated its own host (A) records. In order to ensure that
> its DS-integrated peer DNS servers are able to replicate with this server,
> an attempt was made to update them with the new records through dynamic
> update. An error was encountered during this update, the record data is
> the
> error code.
>
> If this DNS server does not have any DS-integrated peers, then this error
> should be ignored.
>
> If this DNS server's Active Directory replication partners do not have the
> correct IP address(es) for this server, they will be unable to replicate
> with it.
>
> To ensure proper replication:
> 1) Find this server's Active Directory replication partners that run the
> DNS
> server.
> 2) Open DnsManager and connect in turn to each of the replication
> partners.
>
> i using win2003 and exchange 2003 , after i drpromo another win2003 to DC
> ,
> then show these error message
>
>

yes , AD already integrated
not a dns server
is a aditional server , also is DC
not a new domain
same subnet
i can post result

when i use dcdiag , this show failed test frsevent and systemlog
an error event occured . eventID: 0x00000457
server name failed test systemlog

then another all is pass

thx


"Jorge Silva" <(E-Mail Removed)> ¦b¶l¥ó
news:(E-Mail Removed) ¤¤¼¶¼g...
> Hi
>
> Are your Dns Zones AD integrated?
> Is this new server going to be a Dns Server?
> Is this server an aditional server for the same domain or did you created
a
> new domain?
> Is in same subnet?
> Can you post the results for ipconfig /all
>
>
> --
> I hop that helps
>
> Good Luck
> Jorge Silva
> MCSA
> Systems Administrator
>
>
>
>
>
> "Tequila" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > DNS server has updated its own host (A) records. In order to ensure
that
> > its DS-integrated peer DNS servers are able to replicate with this
server,
> > an attempt was made to update them with the new records through dynamic
> > update. An error was encountered during this update, the record data is
> > the
> > error code.
> >
> > If this DNS server does not have any DS-integrated peers, then this
error
> > should be ignored.
> >
> > If this DNS server's Active Directory replication partners do not have
the
> > correct IP address(es) for this server, they will be unable to replicate
> > with it.
> >
> > To ensure proper replication:
> > 1) Find this server's Active Directory replication partners that run the
> > DNS
> > server.
> > 2) Open DnsManager and connect in turn to each of the replication
> > partners.
> >
> > i using win2003 and exchange 2003 , after i drpromo another win2003 to
DC
> > ,
> > then show these error message
> >
> >
>
>

Hi
Is the server pointing to the right Dns Server IPAddress?

To check for the SYSVOL share, at the command prompt, type:
net share

C$ C:\ Default share
IPC$ Remote IPC
ADMIN$ C:\WINDOWS Remote Admin
NETLOGON C:\WINDOWS\SYSVOL\sysvol\domain01.root\SCRIPTS Logon
server share
SYSVOL C:\WINDOWS\SYSVOL\sysvol Logon server share

if the sysvol and / or netlogon shares are not available type - net stop
netlogon & net start netlogon
You should make the new Dc also a Dns Server.

post the reults for ipconfig /all


--
I hop that helps

Good Luck
Jorge Silva
MCSA
Systems Administrator





"Tequila" <(E-Mail Removed)> wrote in message
news:u9oGu$(E-Mail Removed)...
> yes , AD already integrated
> not a dns server
> is a aditional server , also is DC
> not a new domain
> same subnet
> i can post result
>
> when i use dcdiag , this show failed test frsevent and systemlog
> an error event occured . eventID: 0x00000457
> server name failed test systemlog
>
> then another all is pass
>
> thx
>
>
> "Jorge Silva" <(E-Mail Removed)> ¦b¶l¥ó
> news:(E-Mail Removed) ¤¤¼¶¼g...
>> Hi
>>
>> Are your Dns Zones AD integrated?
>> Is this new server going to be a Dns Server?
>> Is this server an aditional server for the same domain or did you created
> a
>> new domain?
>> Is in same subnet?
>> Can you post the results for ipconfig /all
>>
>>
>> --
>> I hop that helps
>>
>> Good Luck
>> Jorge Silva
>> MCSA
>> Systems Administrator
>>
>>
>>
>>
>>
>> "Tequila" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>> > DNS server has updated its own host (A) records. In order to ensure
> that
>> > its DS-integrated peer DNS servers are able to replicate with this
> server,
>> > an attempt was made to update them with the new records through dynamic
>> > update. An error was encountered during this update, the record data
>> > is
>> > the
>> > error code.
>> >
>> > If this DNS server does not have any DS-integrated peers, then this
> error
>> > should be ignored.
>> >
>> > If this DNS server's Active Directory replication partners do not have
> the
>> > correct IP address(es) for this server, they will be unable to
>> > replicate
>> > with it.
>> >
>> > To ensure proper replication:
>> > 1) Find this server's Active Directory replication partners that run
>> > the
>> > DNS
>> > server.
>> > 2) Open DnsManager and connect in turn to each of the replication
>> > partners.
>> >
>> > i using win2003 and exchange 2003 , after i drpromo another win2003 to
> DC
>> > ,
>> > then show these error message
>> >
>> >
>>
>>
>
>