TF-3976 Support DNS SRV resolvers without Cloudflare/Google dependency
          #4129
        
          
      
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Issue
#3976
Description
This PR introduces improvements to the
DNS SRVresolution flow by removing the hard dependency onCloudflareandGoogleresolvers.It enhances
DnsLookupManagerto use a multi-priority fallback mechanism including system DNS, public open resolvers(UDP/TCP), andDNS-over-HTTPS (DoH)providers such asQuad9,AdGuard,OpenDNS, andYandex.The goal is to increase privacy, resilience, and independence from
GAFAM-controlledinfrastructure, especially in restrictive or public network environments.Changes
DnsLookupManagerto support prioritized resolver strategy:Resolved
Screen_recording_20251028_112719.webm