Event ID 1196 and 1579, FailoverClustering error onExchange 2010 servers DAG
https://greg67.blogspot.com/2014/08/event-id-1196-and-1579.html
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 8/20/2014 7:24:35 AM
Event ID: 1196
Task Category: Network Name Resource
Level: Error
Keywords:
User: SYSTEM
Computer:
Description:
Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason:
DNS operation refused.
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 8/20/2014 7:24:35 AM
Event ID: 1579
Task Category: Network Name Resource
Level: Warning
Keywords:
User: SYSTEM
Computer:
Description:
Cluster network name resource 'Cluster Name' failed to update the DNS record for name "DAG DNS Name" over adapter 'MAPI Network'. The error code was 'DNS operation refused. (9005)'. Ensure that a DNS server is accessible from this cluster node and contact your DNS server administrator to verify the cluster identity can update the DNS record "DAG DNS Name".
Error:
Event ID 1119: Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: DNS operation refused.
Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.
Event ID 1579: Cluster network name resource 'Cluster Name' failed to update the DNS record for name "DAG DNS Name (DAG.contoso.com)" over adapter 'MAPI Network'. The error code was 'DNS operation refused. (9005)'. Ensure that a DNS server is accessible from this cluster node and contact your DNS server administrator to verify the cluster identity can update the DNS record "DAG DNS Name (DAG.contoso.com)".
Cause:
The cluster name resource which has been added to the DNS prior to setup active passive cluster ( or any type) need to be updated by the Physical nodes on behalf of the resource record itself. When the active node owns the resources it want to update the A record in the DNS database and DNS record which was created won't allow any authenticated user to update the DNS record with the same owner
Solution:
Delete the existing A record for the cluster name and re-create it and make sure select the box says "Allow any authenticated user to update DNS record with the same owner name "Don't worry about breaking anything , this has "ZERO" impact to cluster simply delete the A record and re-create as it is suggested here.
1
After many hours of research have finally solved the problem!
ReplyBy default a cluster will try to register the DNS record to all available DNS servers, including the secondary DNS server (ISPs or other specified DNS). The solution is simple,
1. REMOVE ALL SPECIFIED DNS SERVER EXCEPT YOUR LOCAL DNS SERVER.
2. Open cluster manager, right click on the cluster IP address, and take offline (will not affect your cluster rolls)
3. Right click on tour cluster and click repair. WALLA issue fixed.