7

Questions: how can I get my availability group to be registered as ag-ewgtest.sql.company.com given that my server thinks of itself as server.company.com.

Setup: my SQL Server 2012 availability group is on multiple subnets, similar to what's described at in this MSDN blog article. When I go into Failover Cluster Manager, it shows that name resolution is not yet available:

enter image description here

I then right-click "Name: ag-ewgtest" and choose properties. I check off "Publish PTR records" and it shows me that the full name is ag-ewgtest.company.com.

enter image description here

The problem I have is that I'm only being allowed to update the DNS zone sql.company.com. If I change the DNS name to be ag-ewgtest.sql.company.com then the full name becomes ag-ewgtest.sql.company.com.company.com.

I've tried updating my NIC as:

enter image description here

But hasn't made a difference. How can I change the subdomain that my availability group tries to register itself in?

Glorfindel
  • 2,205
  • 5
  • 19
  • 26
Elijah W. Gagne
  • 705
  • 2
  • 12
  • 22

2 Answers2

5

The Availability Group Listener name is a Computer Name Object (CNO) in Active Directory, not just a DNS entry:

http://technet.microsoft.com/en-us/library/ff367878(v=exchg.150).aspx

Its location in AD determines where it gets registered. If you want to create a different one somewhere else, you can create a DNS CNAME (alias) pointing to the real Availability Group Listener name:

http://technet.microsoft.com/en-us/library/ff625726(v=ws.10).aspx

Brent Ozar
  • 43,325
  • 51
  • 233
  • 390
2

What's the logic behind this requirement from the sysadmin side?

The cluster is going to register the DNS in the same domain that the cluster exists in, not a subdomain of the domain that the cluster is in. You can put a CNAME in place in sql.company.com that points to your DNS name in company.com, but you'll need to be able to update the DNS record in company.com for the cluster to work correctly.

mrdenny
  • 27,106
  • 2
  • 44
  • 81