MongoDB 3.6 introduces the concept of a seed list that is specified using DNS records, specifically SRV and TXT records, to simplify replica set connections. This allows clients to connect to a replica set even if one of the nodes is unavailable, eliminating the need for every client to pass in a complete set of state information for the cluster. The use of SRV records eliminates this requirement, allowing for transparent changes to node IP addresses or names and the addition or removal of cluster members without impacting clients. SRV and TXT records can be created for self-hosted MongoDB clusters using edit access to DNS servers, such as AWS Route 53, enabling easier management of replica sets.