DNS refused Error in Failover cluster !!!

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.
Not sure, What is the issue here? All of a sudden getting error in my cluster. My DNS settings are looks OK.

Hi Karthikeyan R – FGS,
Could you offer us your cluster event ID and original error message, or you can enable the DNS debug log and filter your cluster VIP to get the DNS register error. Please confirm
you are using the enough permission account when you create your cluster, the detail permission require you can refer the following KB:
The related KB:
Using server debug logging options
http://technet.microsoft.com/en-us/library/cc776361(v=ws.10).aspx
Failover Cluster Step-by-Step Guide: Configuring Accounts in Active Directory
http://technet.microsoft.com/en-us/library/cc731002(v=ws.10).aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

DPM 2012 R2 Consistency Check (Replica Inconsistent) Error for Failover Cluster

I have a SCDPM 2012 R2 instance running against a Windows Server 2012 R2 Failover Cluster on the network.
However, any new/migrated Roles/Virtual machines that I add under an existing protection group always gives me an error saying that the replica is inconsistent.
I've verified the following :
1. All windows updates are applied on the cluster hosts & the DPM server.
2. The VSS and DPMRA services are running on the hosts & DPM server.
3. The Windows Server Backup feature has been installed on all the machines as well.
4. The short term storage disks attached to the DPM server are LUNs and there is enough free space on those.
What else am I missing that could be causing the Replica to be inconsistent - considering that these are new VMs on the hosts themselves - is there a way to force a fresh replica to be created?

Do not remove any of the providers they come with the system. There is just something wrong with that VM, your trying to backup, as it could take the initial replica creation.
Check all of the following
1) Make sure you have enough C drive space on the guest - need space to create a snapshot
2) Check the vssadmin list wirters for any errors
If none of the above, rerun the consistency check when no other backup is running. Check the Application log on the host for any vss failures
Ensure you have all the DPM hotfixes - I am compiling a list since i've been thru many DPM issues.
Great product when you get it going but like any product there are bumps in the road :)
ANNCEX

Failover cluster validation errors

We are trying to set up a failover cluster file server between two domain controllers running Windows Server 2012 RC.
When we go through the Validate Configuration wizard, we receive the following errors messages against the Active Directory configuration (names have been changed).
"It could not be determined whether node computer1.example.com is a read only domain controller because of this error: The object does not exist."
and
"Node(s) computer1.example.com computer2.example.com cannot reach a writable domain controller. Please check connectivity of these nodes to the domain controllers."
Does anyone have any ideas why this might be happening? Replication and DNS appear to be working fine for all other services.

I did some tracking down of the problem, and it appears that it stems from the cluster not being able to retrieve the node names. The function specifically is called GetFqdnNodeNamesFromCluster( ).
It can be seen if you run "Get-ClusterLog" while the cluster is in the process of being created. This error seems to be the root of the cluster creation failure. Here is a stacktrace:
PS C:\Users\gamroot> Get-ClusterLog -v
VERBOSE: Connecting to cluster on local computer TESTNODE1.
VERBOSE: at MS.Internal.ServerClusters.Cluster.GetNodes()
at Microsoft.FailoverClusters.PowerShell.FCCmdlet.GetFqdnNodeNamesFromCluster(Cluster cluster, Boolean onlineOnly)
at Microsoft.FailoverClusters.PowerShell.GetClusterLogCommand.WrappedProcessRecord()
at Microsoft.FailoverClusters.PowerShell.FCCmdlet.ProcessRecord()
VERBOSE: at MS.Internal.ServerClusters.Cluster.GetCoreClusterGroup()
at MS.Internal.ServerClusters.SafeFilteredEnumHandle..ctor(Cluster cluster, Boolean filterCoreGroups, Boolean
filterCoreResources)
at MS.Internal.ServerClusters.SafeClusterEnumHandle..ctor(Void* enumHandle, Cluster cluster, ClusterEnumType
enumType, SafeClusterEnumHandleOptions options, SafeClusEnumHandleType safeClusEnumHandleType)
at MS.Internal.ServerClusters.NativeMethods.ClusterOpenEnum(Cluster cluster, ClusterEnumType enumType,
SafeClusterEnumHandleOptions options)
at MS.Internal.ServerClusters.Cluster.GetNodes()
VERBOSE: at MS.Internal.ServerClusters.ClusterRegistryKey.GetValue(String name)
at MS.Internal.ServerClusters.Cluster.GetCoreClusterGroup()
VERBOSE:
Get-ClusterLog : Failed to retrieve the list of nodes for 'TESTCLUSTER1'.
Could not retrieve the core cluster group for the cluster 'TESTCLUSTER1'.
An error occurred while querying the value 'ClusterGroup'.
Element not found
At line:1 char:1
+ Get-ClusterLog -v
+ ~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (:) [Get-ClusterLog], ClusterCmdletException
+ FullyQualifiedErrorId : NotFound,Microsoft.FailoverClusters.PowerShell.GetClusterLogCommand

Network Name Resource Availability - failover cluster error 1196 on Hyper-V 2012 R2 nodes

Hello,
We're getting this error in our even logs of our four node failover cluster, we tried deleting Host A record in DNS management, that did nothing.
Failover cluster event: 1196
"Cluster network name resource 'CAUCrgt8' failed registration of one or more associated DNS name(s) for the following reason: This operation returned because the timeout period expired.
Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server."
And this resource http://technet.microsoft.com/en-us/library/cc773529%28v=WS.10%29.aspx did not help in solving this.
Do you guys have any other suggestions we could try to resolve this error?

Hi Jonas,
Please offer us which platform server you are using, such as if you are using server 2012 please refer the following update first.
Recommended hotfixes and updates for Windows Server 2012-based Failover Clusters - http://support.microsoft.com/kb/2784261
If the update not work please ppply Full Control permissions for the Cluster Name Resources in the DNS console.
More detail information please refer the following article:
Windows Server 2008 Troubleshooting: Event ID 1196 — Microsoft-Windows-FailoverClustering - http://social.technet.microsoft.com/wiki/contents/articles/windows-server-2008-troubleshooting-event-id-1196-microsoft-windows-failoverclustering.aspx
DNS Registration with the Network Name Resource -
http://blogs.msdn.com/b/clustering/archive/2009/07/17/9836756.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.

I am experiencing this error with one of our cluster environment. Can anyone help me in this issue.
The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.
Thanks,
Venu S.
Venugopal S ----------------------------------------------------------- Please click the Mark as Answer button if a post solves your problem!

Hi Venu S,
Based on my research, you might encounter a known issue, please try the hotfix in this KB:
http://support.microsoft.com/kb/928385
Meanwhile since there is less information about this issue, before further investigation, please provide us the following information:
The version of Windows Server you are using
The result of SELECT @@VERSION
The scenario when you get this error
If anything is unclear, please let me know.
Regards,
Tom Li

Server 2008 Hyper-V Failover Cluster Error on Domain Controller Reboot

I am pretty new to Hyper-V virtual but I have 2 Hyper-V Clusters, each with 2 Nodes and a SAN, 1 Physical Domain Controller for failover cluster management and 1 virtual domain controller as backup. All is running well, no issues. I installed
windows updates on the physical DC and upon reboot, got an error 5120 on cluster 2 that says "Cluster Shared Volume 'Volume1' ('Cluster Disk 1') is no longer available on this node because of 'STATUS_CONNECTION_DISCONNECTED(c000020c)'. All I/O will
temporarily be queued until a path to the volume is reestablished. It pointed to the 2nd node in that cluster as being the issue but when I look at it, it is online and all healthy so I don't understand why the error was triggered and if the DC would
go down for a failure, would that node not be able to access the CSV permanently.
Appreciate any help anyone can provide.

Hi mtnbikediver,
In theory, if you has the correct configuration of cluster the DC restart will not cause the CSV down, does your shared storage installed on your DC? Did you run
the cluster validation before you install the cluster? We strongly recommend you run the cluster validation before you build the cluster, same time please install the recommend update of 2008 cluster first.
Recommended hotfixes for Windows Server 2008-based server clusters
http://support.microsoft.com/kb/957311
I found a similar scenario issue the DC restart will effect the cluster network name resource offline, but it is for 2008R2.
Cluster network name resource cannot be brought online when one of the domain controllers is partly down in Windows Server 2008 R2
http://support2.microsoft.com/?id=2860142
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

VM will not boot after moving using Failover Cluster Manager - "a disk read error occurred......"

My current Configuration:
3 node cluster, using clustered shared storage and about 22 VM's.   The Host servers are running 2012 Data Center while all guest are running 2012 Standard. The SAN is EqualLogic and we are using HIT Kit 4.5.
I have a CSV that is running out of space, so I created another CSV so that I could move some of the VM's to a new home.    I tested this by creating a test VM, and moved it successfully 3 times.     I then moved an actual
LIVE VM and while it seemed to move ok, it will now not start.   The message is "a disk read error occurred Press ctrl+alt+del to restart".     I moved the test VM and it failed as well.
I have read several things about this, but nothing seems to relate to my specific issue.   I have verified that VSS is working and free of errors as well.    From the Settings menu for the VM, if I select "Inspect" the drive,
the properties all look fine.    It is a VHDX and both the current file size and maximum disk size seem correct.
The VM's were moved using the "move - virtual machine storage" option within Failover Cluster Manager.
Suggestions?
Thanks.

Lets see if I can answer all of those and I appreciate the brain storming.   This really needs to work, correctly.
1. The Storage is moving.
2.   VM's and SAN are on same device.
3. No, my Clustered Shared Volume, CSV, is out of room, (more one that later)
4. No, I actually have 2 sans grouped together.   However, I'm moving the VM', form one CSV to another CSV on the Same san. EqualLogic PS 6110 is the one I am trying to move VMS around on, and the other SAN not involved in any way except
for it is in a SAN group is an EqualLogic PS6010.
5. No error During move, it took about 5-10 minutes, no error messages.   Note, I did a test and it worked GREAT 3 times.   Now both a live VM, and the test VM are doing the same thing.
6. No, the machine is not to large.   The test making was a 50 gig drive, just 2012 standard installed with updates.   The live VM was a 75 gig VM that was my Trend Micro Server, or anti-virus host.
7. Expand the existing SCV?   Yes I should be able to, but there is an issue there.   The volume was expanded correctly, Equallogic sees the added space, Fail Over cluster manager sees the added space, however disk manager only
sort of does.    When looking at disk manager, there are 2 areas that tell you a little bit about the drive.   The top part and then the bottom part.   The top part only shows 500G, the original size, while the bottom part
says that it is 1 TB in size.   I call Dell's technical support and after they looked at it I was told by the technician that they had seen this a couple of times and the only way to fix it was to move all the VM's to another CSV and delete the troubled
CSV.   I thought about adding more space to the troubled CSV, but its on a production server with about 12 VM's running on it and I did not want to take a chance.   The Trend VM was running on CSV-1 and working fine.
I must admit that the test VM, was on CSV-2.    I moved the Test VM from csv-2 to csv-3 back and forth several times with no errors.   The Trend Server was on CSV-1 and was moved to CSV-3, however it failed. Again, I then moved
the test VM from CSV-2 to CSV-3 and it failed the same way.   I could not test the "TEST - VM" on csv-1 due to csv-1 not having enough space.
8.   I did disable the network from the VM to see if that mattered it did not.
9.   I have not yet had a chance to connect the VHDX to a new VM, but I will do that in about an hour, hopefully.    Once I am able to test that suggestion I will post the results as well.
Again, thanks for all the suggestions and comments, as I had rather have lots to look at and try.   I hope I answered them well enough.
Kenny

Windows server 2012 failover cluster error: Cluster resource 'Virtual Machine Configuration ... of type 'Virtual machine configuration in clustered role ... failed.

I have two windows 2012 host server that are clustered using windows failover cluster feature. Each server is hosting four VMs. When migrating from Host2 to Host1, the migration failed with the following error:
Cluster resource 'Virtual Machine Configuration SCPCSQLSRV01' of type 'Virtual Machine Configuration' in clustered role 'SCPCSQLSRV01' failed. The error code was '0x569' ('Logon failure: the user has not been granted the requested logon type at this computer.').
When this happens, the VM that I was migrating can no longer be started even on the original host. The only remedy is to restart the host server.
Any suggestion on resolving this problem?
Thanks
Ikad

Thanks. The article referred to above gives the solution to my issue. There is a group policy that is applied to the OU where the host servers were placed. Doing gpupdate /force temporarily removes the problem. Unfortunately the NT Virtual Machine\Virtual
Machines account is a special account that cannot be added like other accounts and granted the log on as a service right. The thread
http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/d56f2eae-726e-409a-8813-670a406593e8 contains how it can be added which is by creating a group and running the command
Net localgroup VMTest “NT Virtual Machine\Virtual Machines” /add
to add it to a local group VMTest. VMTest is then assigned the right to log on as a service.
Ikad

MS- WIN SERVER 2008-R2 FAILOVER CLUSTER --ERROR 1127 ,1583

DEARS ,
I HAVE BEEN FACING PROBLEM FOR MY WINDOWS FAIL OVER CLUSTER SCENARIO.
THE ERROR CODES ARE 1127 AND 1583 WHICH ARE STATING THAT
All nodes IPv4 networks should be configured properly.
Nodes which are using Automatic Private IP Address (APIPA) for adapter Cluster.will not be added to the Windows Failover Cluster. If the adapter is to be used by Windows Failover Cluster, the IPv4 properties of the adapter should be changed to allow assignment
of a valid IP address that is not in the APIPA range.
However , I have checked that all of my NIC adapters have valid Static IP addresses. Also , when one of the nodes is down ,it cannot look for another node.
Please advise for the solution.

Hi,
Could you clarify your described “Nodes which are using Automatic Private IP Address (APIPA) for adapter Cluster.will not be added to the Windows Failover Cluster.” Did you
found one of your cluster node “automatically” have the APIPA address? If so, it seems is the IP conflict issue.
If it is not the IP address conflict issue, please try to disable your all the nodes firewall
or AV soft have the event 1583 typically cause by this function incorrect configured.
More information:
Event ID 1127 — Cluster Network Connectivity
http://technet.microsoft.com/en-us/library/dd353958(v=ws.10).aspx
Event ID 1583 — Network Connectivity and Configuration
http://technet.microsoft.com/en-us/library/ee830320(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Failover Cluster (Errors retrieving file shares)

I'm having an issue with Windows Failover Cluster with a Windows Server 2012 R2 machine. I have two cluster nodes (nodeA and nodeB). My issue is that when nodeA is the owner node, and I open failover cluster manager <clusterName> >>
roles >> <fileserver role> >> shares tab it will hang and say that it is loading, but this will occur infinitely. Although when I go to nodeB (not the owner node) and I go to shares it will show me all of the shares that I have. Next when
I go to <clusterName> >> Nodes >> click on Roles tab the information says "There were errors retrieving file shares."
Now when I switch the nobeB to the owner node, I cannot view the shares on that machine but can now view them on nodeA.
We alse have a test network where I have recreated the machines, environment and the failover cluster to as close as the production network as I can except everything works great in the test network

For anybody searching on this later...
I was getting "There were errors retrieving file shares" no matter which node of my cluster
owned the fileshare service. Turns out my problem was that my servers don't have internet access and I had set a system proxy. The fix described in the link below was to exclude the local domain from the proxy.
http://blogs.technet.com/b/askcore/archive/2012/12/03/cluster-aware-updating-cau-interaction-with-proxy-servers.aspx

Failover Cluster Manager : Add node wizard Error " This operation returned because the timeout period expired" Windows Server 2012

Hi Everybody,
I have two node cluster and trying to add the third node (which is a Virtual Machine), all nodes are in different subnet and can communication with each other. While adding the third node it gives the error at the end of wizard " This operation
returned because the timeout period expired ". My domain controller is 2008 Enterprise Server and nodes are all running Windows Server 2012 Standard Edition. Any idea what is causing the issue.
thanks

Hi,
Before you add a server (node) to a failover cluster, we strongly recommend that you run the Validate a Configuration Wizard for the existing cluster nodes and the new node
or nodes. The Validate a Configuration Wizard helps you confirm the configuration in a variety of important ways. For example, it validates that the server to be added is connected correctly to the networks and storage and that it contains the same software
updates. Please post the error or warning report.
Please try to install the Recommended hotfixes and updates for Windows Server 2012-based failover clusters:
Recommended hotfixes and updates for Windows Server 2012-based failover clusters
http://support.microsoft.com/kb/2784261
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Failover Cluster Validation Report Error with IBM USB Remote NDIS Network device

We are setting up Microsoft Windows Server 2008 R2 Failover Cluster on IBM X3850 X5 and get errors in the Failover cluster Validation Report due to the IBM USB Remote NDIS Network Device is using APIPA adresses and both servers are using same APIPA-adresse.
How should I configure the Server and OS for the Failover cluster to be MS approved?
IBM don't recommend that i disable the Network device, but it is a possible solution!?!

What I did was use ipconfig /all to see the settings it is using and then when and set the ip setting on the NDIS driver to be that except I increment the last value by 1 for each node so that they do not have the same IP address. I ran the
cluster validation again and it came up clean and I have not experienced any issues yet. It does give warnings about it being an Automatic Private IP Address and should not be used, which is ok because we are not going to use it anyways.
Rich Baumet

Network DR test causes Exchange DAG network to fail (Failover Cluster Manager reports comms errors)

We have a DAG configured between 2 mailbox servers, one in each of our main data centres. Our comms team recently performed a DR test between our 2 data centres, switiching from the main production link to the backup link. During this outage the Failover
Cluster Manager reported errors, with each mailbox server reporting the other as uncontactable. The Events that were logged include the following:
Isatap interface isatap.{02ADE20A-D5D4-437F-AD00-E6601F7E7A9D} is no longer active. (EventID 4201)
Cluster node 'MAILBOX_SERVER' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the
Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is
connected such as hubs, switches, or bridges. (EventID 1135)
File share witness resource 'File Share Witness (\\WITNESS_SERVER\SHARE_NAME)' failed to arbitrate for the file share '\\WITNESS_SERVER\SHARE_NAME'. Please ensure that file share '\\WITNESS_SERVER\SHARE_NAME' exists and is accessible by the cluster. (EventID
1564)
Cluster resource 'File Share Witness (\\\WITNESS_SERVER\SHARE_NAME)' in clustered service or application 'Cluster Group' failed. (EventID 1069)
The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. Run the Validate a Configuration wizard to check your network
configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges. (EventID 1177)
The Cluster Service service terminated with service-specific error A quorum of cluster nodes was not present to form a cluster. (EventID 7024)
The Microsoft Exchange Information Store service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. (EventID 7031)
Looking at the Cluster Events in the Failover Cluster Manager Snap-In i see a heap of Event ID 47 (cannot activate the DAG databases as the server is not up according to Windows Failover Cluster Service) and:
Node status could not be recorded. This could prevent some network failure logic from functioning correctly. NodeStatus:IsHealthy=True,HasADAccess=True,ClusterErrorOverrideFalse,LastUpdate=5/2/2011 8:25:42 AMUTC Failure:An Active Manager operation failed.
Error: An error occurred while attempting a cluster operation. Error: Cluster API '"ClusterRegSetValue() failed with 0x6be. Error: The remote procedure call failed"' failed.. (EventID 184)
Forcefully dismounting all the locally mounted databases on server 'BACKUP_MAILBOX_SERVER. (EventID 307).
Our Comms team doesn't believe it is a comms issue as they did not log any network communication errors between the servers in the two sites (using icmp). So if it is not a comms issue, how can I configure the Failover Cluster Manager to be resilient to
this type of network failover event.
Thanks
Dan

Isn't it also true that in a stretched DAG with even numbered nodes, the PAM needs to be in the same site as the active DAG node? If the connection between both nodes goes down, and the PAM is in the "passive" site, the primary node will
dismount the databases since it can't check with the PAM to make sure its safe for it to be up.
In a even-numbered node stretched DAG, the PAM changes to the DR/passive site everytime a failover occurs, but doesn't automatically switch back when you reactivate the primary node.

Windows Server 2012R2 Failover Cluster error with mounted volumes

Hi all,
I've a problem with mounted volume on a WSFC build on top of Windows Server 2012R2, the situation is:
M: is the volume hosting mounting points
disk-1, disk-2, disk-3 are volume mounted on M:\SomeFolder
Theese volumes are used by a SQL Server Failover Cluster Instance, but my problem is related to WSFC. I've set dependencies so disk-1, disk-2, disk-3 depend upon H:
If I try a failover of the role "SQL Server" I observe that when the disk come online in the other node they fail with this error:
Cluster resource 'disk-1' of type 'Physical Disk' in clustered role 'SQL Server (ISQL2014A)' failed. The error code was '0xaa' ('The requested resource is in use.').
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet.
If I manually take offline H: and than bring it online and then manually take online all disk (1 to 3) they come online with no error.
I'm going crazy!

I've found the root of the problem: the servers are virtual machine on a VMware ESX 5.5 infrastructure, VMware claims that on 5.5 multipath is supported for raw device mapping disks but disabling multipath (I've set to fixed path) the Windows Server Failover
Cluster stops to get problems.
Now we have opened a support call with VMware.

IP Resource Errors While Building a Windows Failover Cluster on Azure

I have setup a failover cluster in Microsoft Azure on four VMs. I have two nodes in one subnet/region, one node in another subnet/region and a final node in a third subnet/region. The cluster passed the validation wizard and was successfully built, but the
two nodes in other subnets will not go online, reporting "Failed to bring the resource 'IP Address x.x.x.x' online".
Azure Vnet Setup
Vnet 1 - South Central US - 10.16.16.0/16 - Nodes 1 & 2 - Online
Vnet 2 - West US - 10.116.16.0/16 - Node 3 - Offline
Vnet 3 - East US - 10.216.16.0/16 - Node 4 - Offline
All three IP Address resources are DHCP. I've attempted to make them static but they still failed while coming online. If I click "Information Details" on the error I get:
Error code: 0x80071397
The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource.
It seems to be an issue with the way Azure DHCP works, but I'm stalled. There must be a way to get his working. What am I missing?

Hi Michael Lapidakis,
Starting in Windows Server 2008, a feature called an “OR dependency” was added to Failover Clustering which gave admins the ability to have nodes with a Network Name that
could use one IP Address OR another IP Address .In a multisite cluster, it is expected that 1 IP address is offline as it is an OR relationship.
You can refer the following related article to realize more detail settings of multi-site site cluster IP settings.
IP Resource Errors While Building a Windows Failover Cluster on Azure
https://social.technet.microsoft.com/Forums/en-US/ca2cbf5e-abef-4c23-9cff-7b6ca44acc23/ip-resource-errors-while-building-a-windows-failover-cluster-on-azure?forum=winserverClustering
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

DNS refused Error in Failover cluster !!!

Similar Messages

Maybe you are looking for