Clarity around Service.AutoDiscoveryAddresses for Director in IIS

I have my non-production environment setup for XenApp 7.15 on Windows 2016.  So I went back to review and see what I can do to follow best practices and harden the configuration before handing to QA and starting the production environment.

I am struggling to find recommended IIS settings, so if you have that, please let me know.  In the past we typically adjust the default documents, app settings.

My question though is related to the Delivery Controller.  I currently this setting Service.AutoDiscoveryAddresses seto to localhost, which is not recommended.  So, my question, I'm confused.  When it states you should point to one Controller in the farm, does that mean to itself or a different controller in the farm?  When you have multiple Delivery Controllers should they all have the same Delivery Controller defined here, or ?  

I also see the recommendation to let the Netscaler manage these, https://www.carlstalhood.com/director-load-balancing-netscaler-11-1/, so will get that setup as well.

Could you please provide some clarity.  Thanks in advance.


Settings I'm referencing:

IS Manager, go to Default Web Site > Director > Application Settings, find Service.AutoDiscoveryAddresses, and make sure it points to one Controller in the farm, and not to localhost. From Citrix Docs: Director automatically discovers all other Controllers in the same Site and falls back to those other Controllers if the Controller you specified fails.


In the upgrade options,
In the Delivery Controller page, it will ask you for the location of one Delivery Controller in each farm. Only enter one Delivery Controller per farm. If you have multiple Director servers, each Director server can point to a different Delivery Controller in each farm.
From Citrix Docs: Director automatically discovers all other Delivery Controllers in the same Site and falls back to those other Delivery Controllers if the Controller you specified fails. Click Test Connection, and then click Add.