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>
LVL 5
IndyrbAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
IndyrbAuthor Commented:
found issue on my own
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.