Wednesday, February 11, 2009

Event ID 1196, 1119 DNS operation refused Cluster Servers





We start seeing many event ID's on the cluster servers (Active passive) configuration on one of our client SQL and Exchange servers as fallow below.


Log Name: System

Source: Microsoft-Windows-FailoverClustering

Date: 2/11/2009 4:41:00 PM

Event ID: 1196

Task Category: Network Name Resource

Level: Error

Keywords:

User: SYSTEM

Computer: MCCNPWINSQL01.smtp25.org

Description:

Cluster network name resource 'SQL Network Name (MCCNPSQLDB00)' 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.


Error:

Event id 1196, 1119 FailoverClustering appearing on the clustered Exchange and SQL servers, although the cluster seems to be fine the errors are annoying. Cluster network name resource 'SQL Network Name (MCCNPSQLDB00)' failed to register DNS name 'MCCNPSQLDB00.smtp25.org' over adapter 'Production VLAN 400' for the following reason: DNS operation refused.

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.


Oz ozugurlu MVP (Exchange)

MCITP (EMA), MCITP (EA) MCITP (SA)

MCSE (M+, S+) MCDST,

Security+, Server +, Project+

Blog: smtp25.blogspot.com

Blog: telnet25.wordpress.com

8 comments:

John said...

Thank you, this is a error we have been getting quite a bit on our 2008 R2 SQL Cluster

Anonymous said...

Thank you!

Anonymous said...

Thanks!! I've read about changes in service user, etc but this was the error for me.

Anonymous said...

You can also add the cluster name to the A record security entry, but I like this way better.

Clint Boessen said...

Thanks mate.

Clint Boessen [MVP]

Anonymous said...

Thanks this post has helped me in solving the problem.

we had everyhting done except, "Allow authenticated users" to update records.

all good now.

Albertinho Tomazzoni said...

Very tks! solved!

Anonymous said...

Thanks! Worked!