I was seeing a lot of 1257 errors in our file cluster when we added 3 new nodes. We use static DNS records for pretty much everything that isn't a user endpoint, so I don't need the servers to update anything in DNS. I was able to eliminate the 1257 errors by going in to the NICs on the nodes showing errors, under IPV4 Advanced DNS options, uncheck "Register this connection's addresses in DNS"
Failover Cluster DNS error, event 1257 keeps coming back
Hi,
I have two failover clusters created, for which I did NOT pre-create the DNS records for the cluster or role names.
The DNS records are created when the cluster/role is brought online.
On one of the clusters, I keep getting event ID 1257, where it fails to register or update the DNS entry for the role running on the cluster.
If I delete the existing record, and restart the role, it creates successfully.
I am trying to understand why, if the cluster creates the record, this error keeps coming back?
What can I do to prevent this from constantly complaining about this, when both cluster nodes have access to that DNS record?
Thanks
James
15 answers
Sort by: Most helpful
-
-
Limitless Technology 44,346 Reputation points
2022-03-03T11:52:53.03+00:00 Thank you for your question and reaching out.
I can understand you are facing event 1257 ID of DNS.
Please follow below steps in order to resolve the issue.
- Please delete the CNO ‘A’ record from DNS console.
- Add the same record and verify that “Allow any authenticated user to update DNS record with the same owner name” option is selected.
Hope this answers your question :)
--
--If the reply is helpful, please Upvote and Accept as answer-- -
Joe Bruns 21 Reputation points
2022-07-22T14:46:44.317+00:00 As of 7/22
MS has identified it is indeed an issue on their end. Due to the nature of the 2016 maintenance, they have to examine code from November of 21 to April of 22 to zero in on the culprit and kill the bug.
-
Sivert Solem 16 Reputation points
2022-08-15T13:37:41.677+00:00 We have also experienced this issue.
In our case we have noticed that the cluster attempts to update DNS records using the credentials of a random VCO in the cluster.
A workaround is to put all VCO's in a security group and give the group permission to update DNS entries for all roles in the cluster. -
Robert Berndt 6 Reputation points
2022-08-30T12:26:33.547+00:00 I've seen this on any of our 2016 or newer clusters. The only way I've been able to have it go away is to go into the cluster name in DNS, make sure that the cluster name has "Full Control" of that DNS entry. Then the errors go away.