Resolved DNS records are not cached for subsequent use by new connections

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Works as Designed
    • Priority: Minor - P4
    • 3.0.0
    • Affects Version/s: 2.2.24
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Presently, when a user provides a domain name in their connection string that value is stored (unmodified) internally for use in future connections. That value is resolved at the time of connection creation, without caching the lookup result, which can lead to undesirable situations in the event that the domain potentially returns different IP addresses (e.g. round-robin DNS). Instead, we should cache the result of the DNS lookup for future connections.

            Assignee:
            Matt Broadstone
            Reporter:
            Matt Broadstone
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: