• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6708
  • Last Modified:

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-FailoverClustering
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-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
    <EventID>1196</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>19</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2012-03-27T20:12:59.076339500Z" />
    <EventRecordID>62300</EventRecordID>
    <Correlation />
    <Execution ProcessID="2096" ThreadID="6296" />
    <Channel>System</Channel>
    <Computer>server.domain.com</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="ResourceName">ORSQLDB</Data>
    <Data Name="StatusString">DNS RR set that ought not exist, does exist.
</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-FailoverClustering
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-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
    <EventID>1579</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>19</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2012-03-27T20:12:59.067549200Z" />
    <EventRecordID>62299</EventRecordID>
    <Correlation />
    <Execution ProcessID="2096" ThreadID="6296" />
    <Channel>System</Channel>
    <Computer>server.domain.com</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="ResourceName">ORSQLDB</Data>
    <Data Name="DnsName">ORSQLDB.domain.com</Data>
    <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="BinaryParameterLength">4</Data>
    <Data Name="BinaryData">2F230000</Data>
  </EventData>
</Event>
0
Indyrb
Asked:
Indyrb
  • 3
  • 2
1 Solution
 
Paul MacDonaldDirector, Information SystemsCommented:
If the server is dual-homed, try disconnecting one of the network connections.

I presume the server(s) can see their DNS server?
0
 
IndyrbAuthor Commented:
Yes the server is dual homed,

(1) nic for the private heartbeat
And one nic for the production Lan
0
 
Paul MacDonaldDirector, Information SystemsCommented:
Make sure the Production NIC has priority and that the Heartbeat NIC isn't set up to use DNS/DHCP.
0
 
IndyrbAuthor Commented:
I found the issue, there was a CNAME record pointing to wrong IP address.
0
 
IndyrbAuthor Commented:
found issue on my own
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now