DNS ERRORS after introduction of new server
Tony Purewall
HI
I performed the following
I had a old server running as my Domain Controller , with DNS as AD integrated . Everything was fine .. super dandy.
Then I decided to phase out the old whitebox server for a brand new spanking HP ML350 G4
Well I thought easy job right?
But this again is me !!! I never be as good as you guys at computers doesn’t matter if I spend all my time like I do .. geeks like you guys are born I cant be one by trying SUCKS I wanna be one too !!
Well here is what I did
1) Installed Windows 2003 on new server , old server also running Windows 2003
2) Made the new server a member server in the domain
3) Installed DNS on new server , made it primary in the same zone as old server which had AD integrated DNS – local.lmdg.com
4) Made new server a DC
5) After a while I couldn’t see DNS entries for old server DNS . I thought no transfer of records is happening !!!
6) So I removed DNS and re-installed it again on new server again this time as AD integrated since I choose the right option this time!!!!
7) I saw all the entries after a while
8) I transferred FMSO roles and GC
9) Clients logged on fine
10) I dcpromo old white box server , removed DNS left it as a member server for a few days
11) Clients logged on fine still
12) I reformatted old server , using it as my WUS server now
13) When I reboot my new HP server , my only DC with DNS AD integrated and DHCP
14) The event log for DNS shows the below errors
PLEASE help me clear these since my boss , has seen them and wants to know what happened !!! I am gona be flipping burgers at burger king soon !!! HELP
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4515
Date: 27/03/2005
Time: 12:10:39 PM
User: N/A
Computer: LMDG-DC01
Description:
The zone local.lmdg.com was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition DomainDnsZones.LOCAL.LMDG.COM. The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible.
If an administrator has moved this zone from one directory partition to another this may be a harmless transient condition. In this case, no action is necessary. The deletion of the original copy of the zone should soon replicate to this server.
If there are two copies of this zone in two different directory partitions but this is not a transient caused by a zone move operation then one of these copies should be deleted as soon as possible to resolve this conflict.
To change the replication scope of an application directory partition containing DNS zones and for more details on storing DNS zones in the application directory partitions, please see Help and Support.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 89 25 00 00 %..
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4515
Date: 27/03/2005
Time: 12:10:39 PM
User: N/A
Computer: LMDG-DC01
Description:
The zone _msdcs.local.lmdg.com was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition ForestDnsZones.LOCAL.LMDG.COM. The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible.
If an administrator has moved this zone from one directory partition to another this may be a harmless transient condition. In this case, no action is necessary. The deletion of the original copy of the zone should soon replicate to this server.
If there are two copies of this zone in two different directory partitions but this is not a transient caused by a zone move operation then one of these copies should be deleted as soon as possible to resolve this conflict.
To change the replication scope of an application directory partition containing DNS zones and for more details on storing DNS zones in the application directory partitions, please see Help and Support.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 89 25 00 00 %..
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4515
Date: 27/03/2005
Time: 12:10:39 PM
User: N/A
Computer: LMDG-DC01
Description:
The zone 0.0.10.in-addr.arpa was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition ForestDnsZones.LOCAL.LMDG.COM. The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible.
If an administrator has moved this zone from one directory partition to another this may be a harmless transient condition. In this case, no action is necessary. The deletion of the original copy of the zone should soon replicate to this server.
If there are two copies of this zone in two different directory partitions but this is not a transient caused by a zone move operation then one of these copies should be deleted as soon as possible to resolve this conflict.
To change the replication scope of an application directory partition containing DNS zones and for more details on storing DNS zones in the application directory partitions, please see Help and Support.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 89 25 00 00 %..
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4010
Date: 27/03/2005
Time: 12:10:40 PM
User: N/A
Computer: LMDG-DC01
Description:
The DNS server was unable to create a resource record for 6633c926-e97f-441a-8cd7-9c9dae32dca2._msdcs.local.lmdg.com. in zone local.lmdg.com. The Active Directory definition of this resource record is corrupt or contains an invalid DNS name. The event data contains the error.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 00 00 00 {...
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4010
Date: 27/03/2005
Time: 12:10:40 PM
User: N/A
Computer: LMDG-DC01
Description:
The DNS server was unable to create a resource record for de5e671a-1d30-4103-b581-75b4d2a4dd29._msdcs.local.lmdg.com. in zone local.lmdg.com. The Active Directory definition of this resource record is corrupt or contains an invalid DNS name. The event data contains the error.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 00 00 00 {...
Event Type: Information
Event Source: DNS
Event Category: None
Event ID: 2
Date: 27/03/2005
Time: 12:10:40 PM
User: N/A
Computer: LMDG-DC01
Description:
The DNS server has started.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
![Kevin D. Goodknecht Sr. [MVP]'s profile photo](https://lh3.googleusercontent.com/a/default-user=s40-c)
Kevin D. Goodknecht Sr. [MVP]
Tony Purewall <tonypu...@hotmail.com> commented
Then Kevin replied below:
> HI
>
> I performed the following
>
> I had a old server running as my Domain Controller , with
> DNS as AD integrated . Everything was fine .. super dandy.
>
> Then I decided to phase out the old whitebox server for a
> brand new spanking HP ML350 G4
>
> Well I thought easy job right?
>
> But this again is me !!! I never be as good as you guys
> at computers doesn't matter if I spend all my time like I
> do .. geeks like you guys are born I cant be one by
> trying SUCKS I wanna be one too !!
>
> Well here is what I did
>
> 1) Installed Windows 2003 on new server , old
> server also running Windows 2003
>
> 2) Made the new server a member server in the domain
>
> 3) Installed DNS on new server , made it primary in
You're getting this event because you created a new zone in Active
Directory, when there was already one in AD from the other DC.
What you should have done is installed DNS, not created the zone and let the
zone already in AD replicate.
Event ID 4515 is logged in the DNS Server log in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q867464
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
Tony Purewall
"Tony Purewall" <tonypu...@hotmail.com> wrote in message
news:tonypu...@hotmail.com:
> Hi Kevin
>
>
>
> I followed the article and deleted this zone option 2 path since this had
entries from my old pc names when I upgraded my old server from NT4
and I have rename all the pcs to the names shown in option1
>
>
>
> When I rebooted I still get the errors exactly as before , I no longer
have the zone in option2 in adsiedit.msc but this
>
>
>
>
>
> Name Class Distinguished Name
>
> CN=LostAndFound lostAndFound CN=LostAndFound,DC=DomainDnsZones,DC=LOCAL,DC=LMDG,DC=COM
>
> CN=NTDS Quotas msDS-QuotaContainer
CN=NTDS Quotas,DC=DomainDnsZones,DC=LOCAL,DC=LMDG,DC=COM
>
>
CN=Infrastructure infrastructureUpdate CN=Infrastructure,DC=DomainDnsZones,DC=LOCAL,DC=LMDG,DC=COM
>
>
>
>
>
> Why am I still getting the error?
>
>
>
> Tony
"Kevin D. Goodknecht Sr. [MVP]" <ad...@nospam.WFTX.US> wrote in
message news:ad...@nospam.WFTX.US:
Kevin D. Goodknecht Sr. [MVP]
> message
> news:tonypu...@hotmail.com:
>
>> Hi Kevin
>>
>>
>>
>> I followed the article and deleted this zone option 2
>> path since this had entries from my old pc names when I
>> upgraded my old server from NT4 and I have rename all
>> the pcs to the names shown in option1
>>
>>
>>
>> When I rebooted I still get the errors exactly as before
>> , I no longer have the zone in option2 in adsiedit.msc
>> but this
You may try to do a full reinstall of the AD zones.
Make sure the DC has only its own address listed for DNS.
Change any zones for the AD domain to standard primay (not stored in AD)
This includes the _msdcs.dnsdomainname zone, if it has one, allow dynamic
updates.
Delete the zone objects from ADU&C System\MicrosoftDNS container.
If you have a zone name _msdcs.dnsdomainname make sure the dnsdomainname
zone has a delegation named _msdcs with only an NS record for itself.
Run this from a command line:
net stop dns & net start dns & ipconfig /flushdns & net stop netlogon & net
start netlogon & ipconfig /registerdns.
Then run netdiag /test:dns /v look for errors, if you have errors run
netdiag /fix and rerun netdiag /test:dns /v
In a single DC envirionment you may receive 4004 events at startup if you
use zones stored in AD. you may want to leave the zone type as standard
primary to alleviate these errors. If zone security is a concern, or if you
plan to add a replica DC, convert the zones to AD integrated with only
secure updates allowed. If you add a replica DC, don't create the zones,
just point the replica DC to this one for DNS only, run dcpromo, install DNS
and wait for the zones to replicate. Don't get ahead of yourself by creating
another zone manually.
Tony Purewall
"Kevin D. Goodknecht Sr. [MVP]" <ad...@nospam.WFTX.US> wrote in message
news:ad...@nospam.WFTX.US:
> In news:OYqZCDcN...@TK2MSFTNGP12.phx.gbl,
Kevin D. Goodknecht Sr. [MVP]
> is too large?
Email them to me using the directions in my signature line.