• Status: Solved
  • Priority: Low
  • Security: Public
  • Views: 109
  • Last Modified:

Creating SQL server 2016 listener

hi,

I am right now try to create a SQL server 2016 listener by reading this:

https://www.sqlshack.com/alwayson-availability-groups-how-to-setup-ag-between-a-clustered-and-standalone-instance-part-3/

question is :

1)  in the article above:

" To create a listener, we will also need an IP and Computer in the AD, and don’t forget that the cluster computer should have full access to the SQL Server computer account."

I am now have and IP address and a computer name (name only), is that mean that Computer name must exists in the AD for it to works? currently that computer name is not register in the AD.

now I am created a SQL 2016 AOG in a domain less configuration and I am not sure if listener will work in this case.

2) to create the listener, should/must the SQL server need to join the AD too ?

3)
when creating the listener on the wizard shown in the link above:

"A new window will be opened. Fill the “Listener DNS Name” with the name of your AD Computer Name. In our case SQLSRVAG01. In the “Port” field, choose an adequate port, something that is not being used.

what is listener DNS name ?  the listener name I have ? e.g. SQLSERVERListener ? do I need domain surfix for it?  

I can't create one using that name only and the error is :

listener error.
0
marrowyung
Asked:
marrowyung
  • 8
  • 6
1 Solution
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
It's the listener name already created in the Active Directory (AD)?
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
hi,

it is just a name i reserved for the listener. so is that mean this name, virtual name, MUST register in AD?  so this also means SQL server has to join domain too ?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
You shouldn't pre register nothing. The SQL Server service account should have write permissions in the active directory to create the listener name (DNS entry).
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
marrowyungSenior Technical architecture (Data)Author Commented:
so this means the add listener wizard will create the respective name and register in AD itself ?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Yes. The error you're getting it looks to me that is because the listener name has been already created.
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
" The error you're getting it looks to me that is because the listener name has been already created. "

I thought it is a WSFC depending service error ?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Read the error again. It says "The DNS name may have been taken or have a conflict with existing name services...".
WSFC only means that your using a cluster.
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
"WSFC only means that your using a cluster. "

yeah, but AOG is depending on this, right?

" listener name has been already created. "

so this means we have to remove it from AD and then let Add listener wizard to recreate it ?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
so this means we have to remove it from AD and then let Add listener wizard to recreate it ?
Correct.
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
I am checking on this ! as I am installed SQL server in domain less environment and I just worry about I can't change it to join back AD, which should solve all problem, agree?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Sorry, I don't have experience in installing SQL Server in a domain less environment so I can't confirm that you won't have issues.
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
yeah, tks for it anyway!  I think this configuration gives trouble, I probably join back domain very soon !
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
I researched a lot, it seems that it is all related to AD, without AD, SQL listener can't create!

but it is funny that with SQL 2016 domain less AOG, SQL listener still relies on AD!!
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
tks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

  • 8
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now