Skip to main content

Exercising Name Resolution with Delphix Network Latency Test (KBA5306)




KBA# 5306



SnapSync, VDB provision, or Environment creation may fail if the Delphix Engine encounters an issue resolving a hostname or fully qualified domain name (FQDN).  This typically indicates a problem with the configured DNS server (or possibly a simple typo of the host address). In these instances, it can be useful to manually exercise name resolution and provide additional detail to the network admin team.

As the Delphix Engine CLI and GUI do not provide all standard network diagnostic tools (such as traceroute, nslookup), the CLI Network Latency Test can be used to quickly validate name resolution on-demand.

Please note, this method does not provide the same options to query a specific DNS server, or detail the server IP responding as nslookup does from another OS, but can be used as one step in troubleshooting.

Applicable Delphix Versions

Click here to view the versions of the Delphix engine to which this article applies
Major Release All Sub Releases




5.0,,,,,,,,, ,,,,,


4.2,,,,,,, ,,



The Delphix Admin GUI interface for Network Latency test only provides the ability to select an existing Environment.  To utilize the network latency test via CLI, ssh to the Engine with any Delphix Admin account, and navigate to /network test latency.

delphixEngine> network test latency
delphixEngine network test latency> create

Create a new network test, and set the remoteAddress parameter to the hostname or FQDN you wish to check name resolution.  Note, in this interface both remoteAddress and remoteHost are available... the remoteHost parameter only accepts an existing Environment name, so remoteAddress allows any entry.

If the hostname or FQDN can be resolved, the latency test will start and complete successfully.  If the hostname or FQDN cannot be resolved, an error will be received indicating the entry is not a valid hostname or IP address.  Examples of a successful and a failed test are provided below to illustrate.

delphixEngine network test latency create *> set
delphixEngine network test latency create *> commit
    Dispatched job JOB-217
    NETWORK_LATENCY_TEST_EXECUTE job started for "".
    Executing network latency test.
    NETWORK_LATENCY_TEST_EXECUTE job for "" completed successfully.
delphixEngine network test latency> create
delphixEngine network test latency create *> set
delphixEngine network test latency create *> commit
   Error: "" is not a valid hostname or IP address.
  Action: Make sure that any hostname provided resolves to a valid IP address and that the Delphix Engine's DNS configuration is correct.

Further, a test that completes successfully can be reviewed to check the IP address resolved via DNS, by reviewing the details of the test.  In the example below, the test named "" that completed successfully is reviewed.  The remoteAddress parameter displays the IP address used for the test to complete.

Please note this does not provide a comprehensive method to view multiple IP addresses resolved by a host name or FQDN.

delphixEngine network test latency> ls
NAME                                             STATE      AVERAGE  COMPLETED  20112usec

delphixEngine network test latency> select 
delphixEngine network test latency ''> ls
    type: NetworkLatencyTest
    average: 20112usec
    endTime: 2020-05-20T22:03:14.905Z
    loss: 0
    maximum: 20558usec
    minimum: 19789usec
        type: NetworkLatencyTestParameters
        requestCount: 20
        requestSize: 16B
    reference: NETWORK_LATENCY_TEST-1
    startTime: 2020-05-20T22:02:38.184Z
    state: COMPLETED
    stddev: 323usec

DNS server configuration details are not accessible through the Delphix Admin interfaces; as this is a system configuration parameter, only the System Setup interface provides these configuration details.


delphixEngine> network
delphixEngine network> setup
delphixEngine network setup> ls
    defaultRoute: <redacted gateway>
    dhcp: true
    dnsServers: <redacted server1>,<redacted DNS server2>
    hostname: delphixEngine
    primaryAddress: <redacted address>/19

Any changes to the DNS server configuration can also be completed through GUI or CLI (Only possible if static interface is configured, ie DHCP:false)