question

Currently, we are running SQL Server 2016 in our environment. And, we are planning to upgrade it to SQL Server 2017. We have configured mirroring(asynchronous) for our Disaster Recovery setup, and the primary and Secondary servers are located in two different cities. Since mirroring is discontinued with this version, we are moving to Alwayson Availablility Group. Principal Server's HostName: SRVDB1 Disaster Server's HostName: SRVDB2 Principal Server's DNS Name: INTRADB We use the above DNS name of database server in the following areas. 1) Connection strings of the web applications. 2) There are several excel and CSV files generated on daily basis through some SQL Jobs and are placed on the same database server, and later they will be moved some other servers. To access the generated files from other servers we use the network path(\INTRADB). 3) LinkedServers that are created on other servers to connect the mentioned database server. If we assign the listener the same DNS Name(after removing it from Database Server), we can connect the databases added to the Availability group, no doubt on that. The questions now arises are, 1) How the above three areas will work if the DNS name(INTRADB, which is now assigned with the database server) is assigned to the Listener. 2) We don't need any readable secondaries for our environment. Do we still require Listener for our setup. 3) If our setup doesn't require Listener, then can we assign the DNS name to cluster name, so that, we don't want to do any change on connection strings and the way we access the files. If this is the case, then do we face any challange during the time of planned/forced Manual failover.