Setting DNS Lookups in the Target Editor

How to

  1. To override DNS lookup at the target-level, first open the target in the Target Editor. If you're not sure of the target to modify, inspect your clip(s) in the Clip Editor lower panel, Message/Actions tab, Included Targets list (you can double-click an included target to open it in the editor).
  2. In the open target, locate the DNS Options section. The Target Editor > DNS Options section includes the ability to set a DNS server per target, and also to specify the lookup's Minimum and Maximum Time to Live (TTL), in the Target Editor.
  3. To use DNS lookups, check the "This Target performs its own DNS Lookups" box. Once enabled, CloudTest's Maestro DNS Caching layer will perform the lookup traversing from the top level domain and "down" until it can resolve the target's host name to the IP address it should communicate with. Note that this is not a must, just nice to have, and will work with all of the input boxes below left empty.Note: In most cases, it is not necessary to fill in the remaining DNS Server fields (unless the test case specifically requires one). See the DNS Lookup Considerations section above to determine if your test needs the additional settings specified.
  4. Optionally, specify the following settings.TIP: DNS lookups can be used in conjunction with HttpHostOverride settings for environments where load balancing architectures are in place.
    • DNS Server
    Specify the host name or IP address of the DNS name server to use. If none is specified, then a public root name server will be used. Usually, you do not need to set this.
    • DNS Maximum TTL
    Specify the integer, in seconds, for the maximum time to live.
    • DNSMinTTL
    This sets the minimum amount of time that any DNS result will be cached. This setting can increase the amount of time that a result would normally be cached, if it is more than the TTL specified in an actual DNS result. If 0, then result caching will be disabled completely. If -1, then results will be cached up to the amount of time specified in the DNS result, with no minimum. This setting can be used to mimic the behavior of browsers such as Internet Explorer, which cache longer than the DNS result says to cache.


  5. Save the target after making any changes.