Indyrb
asked on
Failover Cluster issues
Getting errors in Failover cluster manager,
also shows resource online (Name resolution Not yet Available)
Here are some events, need help fixing issue
Log Name: System
Source: Microsoft-Windows-Failover Clustering
Date: 3/27/2012 4:12:59 PM
Event ID: 1196
Task Category: Network Name Resource
Level: Error
Keywords:
User: SYSTEM
Computer: server.domain.com
Description:
Cluster network name resource 'ORSQLDB' failed registration of one or more associated DNS name(s) for the following reason:
DNS RR set that ought not exist, does exist.
.
Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Fa iloverClus tering" Guid="{BAF908EA-3421-4CA9- 9B84-6689B 8C6F85F}" />
<EventID>1196</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>19</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000 00</Keywor ds>
<TimeCreated SystemTime="2012-03-27T20: 12:59.0763 39500Z" />
<EventRecordID>62300</Even tRecordID>
<Correlation />
<Execution ProcessID="2096" ThreadID="6296" />
<Channel>System</Channel>
<Computer>server.domain.co m</Compute r>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="ResourceName">ORSQLD B</Data>
<Data Name="StatusString">DNS RR set that ought not exist, does exist.
</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-Failover Clustering
Date: 3/27/2012 4:12:59 PM
Event ID: 1579
Task Category: Network Name Resource
Level: Warning
Keywords:
User: SYSTEM
Computer: server.domain.com
Description:
Cluster network name resource 'ORSQLDB' failed to update the DNS record for name 'ORSQLDB.domain.com' over adapter 'Local Area Connection'. The error code was 'DNS RR set that ought not exist, does exist. (9007)'. 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 'ORSQLDB.domain.com'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Fa iloverClus tering" Guid="{BAF908EA-3421-4CA9- 9B84-6689B 8C6F85F}" />
<EventID>1579</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>19</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000 00</Keywor ds>
<TimeCreated SystemTime="2012-03-27T20: 12:59.0675 49200Z" />
<EventRecordID>62299</Even tRecordID>
<Correlation />
<Execution ProcessID="2096" ThreadID="6296" />
<Channel>System</Channel>
<Computer>server.domain.co m</Compute r>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="ResourceName">ORSQLD B</Data>
<Data Name="DnsName">ORSQLDB.dom ain.com</D ata>
<Data Name="Status">DNS RR set that ought not exist, does exist. (9007)</Data>
<Data Name="AdapterName">Local Area Connection</Data>
<Data Name="IP Address">1.2.3.4</Data>
<Data Name="BinaryParameterLengt h">4</Data >
<Data Name="BinaryData">2F230000 </Data>
</EventData>
</Event>
also shows resource online (Name resolution Not yet Available)
Here are some events, need help fixing issue
Log Name: System
Source: Microsoft-Windows-Failover
Date: 3/27/2012 4:12:59 PM
Event ID: 1196
Task Category: Network Name Resource
Level: Error
Keywords:
User: SYSTEM
Computer: server.domain.com
Description:
Cluster network name resource 'ORSQLDB' failed registration of one or more associated DNS name(s) for the following reason:
DNS RR set that ought not exist, does exist.
.
Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Fa
<EventID>1196</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>19</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2012-03-27T20:
<EventRecordID>62300</Even
<Correlation />
<Execution ProcessID="2096" ThreadID="6296" />
<Channel>System</Channel>
<Computer>server.domain.co
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="ResourceName">ORSQLD
<Data Name="StatusString">DNS RR set that ought not exist, does exist.
</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-Failover
Date: 3/27/2012 4:12:59 PM
Event ID: 1579
Task Category: Network Name Resource
Level: Warning
Keywords:
User: SYSTEM
Computer: server.domain.com
Description:
Cluster network name resource 'ORSQLDB' failed to update the DNS record for name 'ORSQLDB.domain.com' over adapter 'Local Area Connection'. The error code was 'DNS RR set that ought not exist, does exist. (9007)'. 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 'ORSQLDB.domain.com'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Fa
<EventID>1579</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>19</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2012-03-27T20:
<EventRecordID>62299</Even
<Correlation />
<Execution ProcessID="2096" ThreadID="6296" />
<Channel>System</Channel>
<Computer>server.domain.co
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="ResourceName">ORSQLD
<Data Name="DnsName">ORSQLDB.dom
<Data Name="Status">DNS RR set that ought not exist, does exist. (9007)</Data>
<Data Name="AdapterName">Local Area Connection</Data>
<Data Name="IP Address">1.2.3.4</Data>
<Data Name="BinaryParameterLengt
<Data Name="BinaryData">2F230000
</EventData>
</Event>
ASKER
Yes the server is dual homed,
(1) nic for the private heartbeat
And one nic for the production Lan
(1) nic for the private heartbeat
And one nic for the production Lan
Make sure the Production NIC has priority and that the Heartbeat NIC isn't set up to use DNS/DHCP.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
found issue on my own
I presume the server(s) can see their DNS server?