Missing A records in Zone
I have the following: Server A -- W2k3 with AD/ DHCP/DNS First DC
Server B -- W2k3 with AD (just added for redudancy)
All looks good so far. I decided to add DNS to Server B for redundancy as well. Everything appears to have populated except my Forward lookup zone records. All that shows is Server B. I created the zone using the wizard. It is an AD Integrated Primary. I also received some errors in Server B's DNS events. The most recent warning is:
The zone mydomain.net was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition DomainDnsZones.mydomain.ne
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.
Any ideas? Should I have not created the zone on the second machine?
--SM
Server B -- W2k3 with AD (just added for redudancy)
All looks good so far. I decided to add DNS to Server B for redundancy as well. Everything appears to have populated except my Forward lookup zone records. All that shows is Server B. I created the zone using the wizard. It is an AD Integrated Primary. I also received some errors in Server B's DNS events. The most recent warning is:
The zone mydomain.net was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition DomainDnsZones.mydomain.ne
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.
Any ideas? Should I have not created the zone on the second machine?
--SM
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
zsaurabh
Just do ipconfig /flushdns and /registerdns. it will create A record
ASKER
I installed this yesterday so I assume replication has taken place (if it can).
Server A has everything and no DNS events.
Server B has Reverse lookup records and some other items similar to the zone in Server A, in particular
_msdcs.mydomain.net folder.
What next... would the other error explanations help?
Server A has everything and no DNS events.
Server B has Reverse lookup records and some other items similar to the zone in Server A, in particular
_msdcs.mydomain.net folder.
What next... would the other error explanations help?
ASKER
Would something like this work on Server B (Courtesy of MarkZZZ):
-convert dns to primary zone (uncheck integrate with active directory)
-remove dns in configure your server
-remove dns folder from system32
-in system32\config remove netlogon.dnb and netlogon.dns
reinstall dns (configure your server) with the correct zone name
then at the command prompt:
ipconfig /registerdns
net stop netlogon
net start netlogon
-SM
-convert dns to primary zone (uncheck integrate with active directory)
-remove dns in configure your server
-remove dns folder from system32
-in system32\config remove netlogon.dnb and netlogon.dns
reinstall dns (configure your server) with the correct zone name
then at the command prompt:
ipconfig /registerdns
net stop netlogon
net start netlogon
-SM
ASKER
Intial errors at zone creation. Note-- The original warning came after Stopping DNS and restarting it.
1st Error before most recent warning:
The DNS server was unable to add or write an update of domain name dc1 in zone mydomain.net to the Active Directory. Check that the Active Directory is functioning properly and add or update this domain name using the DNS console. The extended error debug information (which may be empty) is "0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
'CN=MicrosoftDNS,CN=System
2nd Error before most recent warning:
The DNS server was unable to add or write an update of domain name dc1 in zone mydomain.net to the Active Directory. Check that the Active Directory is functioning properly and add or update this domain name using the DNS console. The extended error debug information (which may be empty) is "0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
'CN=MicrosoftDNS,CN=System
3rd Error before most recent warning:
The DNS server was unable to add or write an update of domain name mydomain in zone mydomain.net to the Active Directory. Check that the Active Directory is functioning properly and add or update this domain name using the DNS console. The extended error debug information (which may be empty) is "0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
'CN=MicrosoftDNS,CN=System
Hope this helps --SM
1st Error before most recent warning:
The DNS server was unable to add or write an update of domain name dc1 in zone mydomain.net to the Active Directory. Check that the Active Directory is functioning properly and add or update this domain name using the DNS console. The extended error debug information (which may be empty) is "0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
'CN=MicrosoftDNS,CN=System
2nd Error before most recent warning:
The DNS server was unable to add or write an update of domain name dc1 in zone mydomain.net to the Active Directory. Check that the Active Directory is functioning properly and add or update this domain name using the DNS console. The extended error debug information (which may be empty) is "0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
'CN=MicrosoftDNS,CN=System
3rd Error before most recent warning:
The DNS server was unable to add or write an update of domain name mydomain in zone mydomain.net to the Active Directory. Check that the Active Directory is functioning properly and add or update this domain name using the DNS console. The extended error debug information (which may be empty) is "0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
'CN=MicrosoftDNS,CN=System
Hope this helps --SM
Can you ping the server GUID?
ASKER
From Server A I can successfully ping Server B by GUID
ASKER
I realize upon closer inspection that Server B Zone properties has the Zone Replication Scope set to: To all DOMAIN CONTROLLERS (third option) where Server A is set to all DNS Servers (second option). I understand that the third option is chosen when you are using a mixed environment with WIN 2000 controllers. Can I just change the setting to option 2 and see what happens?
--SM
--SM