doxctl is a diagnostic CLI tool that endusers can use to triage connectivity problems stemming from their VPN & DNS setups on their laptops. It can help with the following areas:
| Area | Description |
|---|---|
| VPN | Can servers be reached over the VPN across geo-locations |
| DNS | Resolvers, search paths, etc. are set |
| Resolvers | VPN defined DNS resolvers are defined and reachable |
| Routing and connectivity | When on the VPN well-known servers are reachable |
Tree - CLICK ME
$ brew install slmingol/tap/doxctl
$ brew install slmingol/tap/doxctl
==> Installing doxctl from slmingol/tap
==> Downloading https://ghcr.io/v2/homebrew/core/go/manifests/1.16.4
######################################################################## 100.0%
==> Downloading https://ghcr.io/v2/homebrew/core/go/blobs/sha256:8aa23b394e05aaef495604670401f9308c01c3c30a1857077493a80d1719e089
==> Downloading from https://pkg-containers.githubusercontent.com/ghcr1/blobs/sha256:8aa23b394e05aaef495604670401f9308c01c3c30a1857077493a80d1719e089?se=202
######################################################################## 100.0%
==> Downloading https://github.com/slmingol/doxctl/releases/download/0.0.27-alpha/doxctl_0.0.27-alpha_Darwin_x86_64.tar.gz
==> Downloading from https://github-releases.githubusercontent.com/367779289/09fcfe00-c133-11eb-9f76-3f053be7f72c?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Cre
######################################################################## 100.0%
==> Installing dependencies for slmingol/tap/doxctl: go
==> Installing slmingol/tap/doxctl dependency: go
==> Pouring go--1.16.4.catalina.bottle.tar.gz
🍺 /usr/local/Cellar/go/1.16.4: 9,956 files, 503.6MB
==> Installing slmingol/tap/doxctl
🍺 /usr/local/Cellar/doxctl/0.0.27-alpha: 5 files, 9.1MB, built in 4 seconds
$ brew search doxctl
==> Formulae
slmingol/tap/doxctl ✔
$ brew update
Updated 2 taps (homebrew/cask and slmingol/tap).
==> Updated Formulae
slmingol/tap/doxctl ✔
==> Deleted Casks
appstudio filedrop hex rss
You have 96 outdated formulae and 10 outdated casks installed.
You can upgrade them with brew upgrade
or list them with brew outdated.
$ brew upgrade doxctl
==> Upgrading 1 outdated package:
slmingol/tap/doxctl 0.0.27-alpha -> 0.0.28-alpha
==> Upgrading slmingol/tap/doxctl 0.0.27-alpha -> 0.0.28-alpha
==> Downloading https://github.com/slmingol/doxctl/releases/download/0.0.28-alpha/doxctl_0.0.28-alpha_Darwin_x86_64.tar.gz
==> Downloading from https://github-releases.githubusercontent.com/367779289/c7d4bc00-c134-11eb-8b3d-622ae425b081?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Cre
######################################################################## 100.0%
🍺 /usr/local/Cellar/doxctl/0.0.28-alpha: 5 files, 9.1MB, built in 4 seconds
Removing: /usr/local/Cellar/doxctl/0.0.27-alpha... (5 files, 9.1MB)
Removing: /Users/smingolelli/Library/Caches/Homebrew/doxctl--0.0.27-alpha.tar.gz... (3.4MB)
$ brew uninstall doxctl
Uninstalling /usr/local/Cellar/doxctl/0.0.27-alpha... (5 files, 9.1MB)
$ doxctl -h
'doxctl' is a collection of tools which can be used to diagnose & triage problems
stemming from the following areas with a laptop or desktop system:
- DNS, specifically with the configuration of resolvers
- VPN configuration and network connectivity over it
- General access to well-known servers
- General access to well-known services
- ... or general network connectivity issues
Usage:
doxctl [command]
Available Commands:
dns Run diagnostics related to DNS servers (aka. resolvers) configurations
help Help about any command
net TBD
svcs TBD
svrs Run diagnostics verifying connectivity to well known servers thru a VPN connection
vpn Run diagnostics related to VPN connections, network interfaces & configurations
Flags:
-c, --config string config file (default is $HOME/.doxctl.yaml)
-h, --help help for doxctl
-v, --verbose Enable verbose output of commands
Use "doxctl [command] --help" for more information about a command.
$ doxctl dns -h
doxctl's 'dns' subcommand can help triage DNS resovler configuration issues,
general access to DNS resolvers and name resolution against DNS resolvers.
Usage:
doxctl dns [flags]
Flags:
-a, --allChk Run all the checks in this subcommand module
-d, --digChk Check if VPN defined resolvers respond with well-known servers in DCs
-h, --help help for dns
-p, --pingChk Check if VPN defined resolvers are pingable & reachable
-r, --resolverChk Check if VPN designated DNS resolvers are configured
Global Flags:
-c, --config string config file (default is $HOME/.doxctl.yaml)
-v, --verbose Enable verbose output of commands
Tree - CLICK ME
$ doxctl dns -r
**NOTE:** Using config file: /Users/smingolelli/.doxctl.yaml
┌───────────────────────────────────────────────────────────────────────────┐
│ VPN defined DNS Resolver Checks │
├──────────────────────────────────────────┬────────────────────────────────┤
│ PROPERTY DESCRIPTION │ VALUE │
├──────────────────────────────────────────┼────────────────────────────────┤
│ DomainName defined? │ unset │
│ SearchDomains defined? │ unset │
│ ServerAddresses defined? │ unset │
└──────────────────────────────────────────┴────────────────────────────────┘
INFO: Any values of unset indicate that the VPN client is not defining DNS resolver(s) properly!
$ doxctl dns -r
**NOTE:** Using config file: /Users/smingolelli/.doxctl.yaml
┌───────────────────────────────────────────────────────────────────────────┐
│ VPN defined DNS Resolver Checks │
├──────────────────────────────────────────┬────────────────────────────────┤
│ PROPERTY DESCRIPTION │ VALUE │
├──────────────────────────────────────────┼────────────────────────────────┤
│ DomainName defined? │ set │
│ SearchDomains defined? │ set │
│ ServerAddresses defined? │ set │
└──────────────────────────────────────────┴────────────────────────────────┘
INFO: Any values of unset indicate that the VPN client is not defining DNS resolver(s) properly!
Tree - CLICK ME
$ doxctl dns -p
**NOTE:** Using config file: /Users/smingolelli/.doxctl.yaml
┌──────────────────────────────────────────────────────────────────────────────────┐
│ VPN defined DNS Resolver Connectivity Checks │
├──────────────────────────────────────────┬───────────────┬───────────────┬───────┤
│ PROPERTY DESCRIPTION │ IP │ NET I/F │ VALUE │
├──────────────────────────────────────────┼───────────────┼───────────────┼───────┤
└──────────────────────────────────────────┴───────────────┴───────────────┴───────┘
WARNING:
Your VPN client does not appear to be defining any DNS resolver(s) properly,
you're either not connected via VPN or it's misconfigured!
$ doxctl dns -p
**NOTE:** Using config file: /Users/smingolelli/.doxctl.yaml
┌──────────────────────────────────────────────────────────────────────────────────┐
│ VPN defined DNS Resolver Connectivity Checks │
├──────────────────────────────────────────┬───────────────┬───────────────┬───────┤
│ PROPERTY DESCRIPTION │ IP │ NET I/F │ VALUE │
├──────────────────────────────────────────┼───────────────┼───────────────┼───────┤
│ Resovler is pingable? │ 10.5.0.18 │ utun2 │ true │
│ Reachable via TCP? │ 10.5.0.18 │ utun2 │ true │
│ Reachable via UDP? │ 10.5.0.18 │ utun2 │ true │
├──────────────────────────────────────────┼───────────────┼───────────────┼───────┤
│ Resovler is pingable? │ 10.5.0.19 │ utun2 │ true │
│ Reachable via TCP? │ 10.5.0.19 │ utun2 │ true │
│ Reachable via UDP? │ 10.5.0.19 │ utun2 │ true │
└──────────────────────────────────────────┴───────────────┴───────────────┴───────┘
Tree - CLICK ME
$ doxctl dns -d
**NOTE:** Using config file: /Users/smingolelli/.doxctl.yaml
┌──────────────────────────────────────────────────────────────────────────────┐
│ Dig Check against VPN defined DNS Resolvers │
├──────────────────────────────────────────┬─────────────────┬─────────────────┤
│ HOSTNAME TO 'DIG' │ RESOLVER IP │ IS RESOLVABLE? │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ idm-01a.lab1.somedom.local │ │ false │
│ idm-01b.lab1.somedom.local │ │ false │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ idm-01a.rdu1.somedom.local │ │ false │
│ idm-01b.rdu1.somedom.local │ │ false │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ idm-01a.atl1.somedom.local │ │ false │
│ idm-01b.atl1.somedom.local │ │ false │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ idm-01a.dfw1.somedom.local │ │ false │
│ idm-01b.dfw1.somedom.local │ │ false │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ idm-01a.lax2.somedom.local │ │ false │
│ idm-01b.lax2.somedom.local │ │ false │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ idm-01a.jfk1.somedom.local │ │ false │
│ idm-01b.jfk1.somedom.local │ │ false │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ SUCCESSESFUL QUERIES │ RESOLVER #1: 0 │ │
│ │ RESOLVER #2: 0 │ │
└──────────────────────────────────────────┴─────────────────┴─────────────────┘
WARNING:
Your VPN client does not appear to be defining any DNS resolver(s) properly,
you're either not connected via VPN or it's misconfigured!
$ doxctl dns -d
**NOTE:** Using config file: /Users/smingolelli/.doxctl.yaml
┌──────────────────────────────────────────────────────────────────────────────┐
│ Dig Check against VPN defined DNS Resolvers │
├──────────────────────────────────────────┬─────────────────┬─────────────────┤
│ HOSTNAME TO 'DIG' │ RESOLVER IP │ IS RESOLVABLE? │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ idm-01a.lab1.somedom.local │ 10.5.0.18 │ true │
│ idm-01b.lab1.somedom.local │ 10.5.0.18 │ true │
│ idm-01a.lab1.somedom.local │ 10.5.0.19 │ true │
│ idm-01b.lab1.somedom.local │ 10.5.0.19 │ true │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ idm-01a.rdu1.somedom.local │ 10.5.0.18 │ true │
│ idm-01b.rdu1.somedom.local │ 10.5.0.18 │ true │
│ idm-01a.rdu1.somedom.local │ 10.5.0.19 │ true │
│ idm-01b.rdu1.somedom.local │ 10.5.0.19 │ true │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ idm-01a.atl1.somedom.local │ 10.5.0.18 │ true │
│ idm-01b.atl1.somedom.local │ 10.5.0.18 │ true │
│ idm-01a.atl1.somedom.local │ 10.5.0.19 │ true │
│ idm-01b.atl1.somedom.local │ 10.5.0.19 │ true │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ idm-01a.dfw1.somedom.local │ 10.5.0.18 │ true │
│ idm-01b.dfw1.somedom.local │ 10.5.0.18 │ true │
│ idm-01a.dfw1.somedom.local │ 10.5.0.19 │ true │
│ idm-01b.dfw1.somedom.local │ 10.5.0.19 │ true │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ idm-01a.lax2.somedom.local │ 10.5.0.18 │ true │
│ idm-01b.lax2.somedom.local │ 10.5.0.18 │ true │
│ idm-01a.lax2.somedom.local │ 10.5.0.19 │ true │
│ idm-01b.lax2.somedom.local │ 10.5.0.19 │ true │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ idm-01a.jfk1.somedom.local │ 10.5.0.18 │ true │
│ idm-01b.jfk1.somedom.local │ 10.5.0.18 │ true │
│ idm-01a.jfk1.somedom.local │ 10.5.0.19 │ true │
│ idm-01b.jfk1.somedom.local │ 10.5.0.19 │ true │
├──────────────────────────────────────────┼─────────────────┼─────────────────┤
│ SUCCESSESFUL QUERIES │ RESOLVER #1: 12 │ │
│ │ RESOLVER #2: 12 │ │
└──────────────────────────────────────────┴─────────────────┴─────────────────┘
$ doxctl vpn -h
doxctl's 'vpn' subcommand can help triage VPN related configuration issues,
& routes related to a VPN connection.
Usage:
doxctl vpn [flags]
Flags:
-a, --allChk Run all the checks in this subcommand module
-h, --help help for vpn
-i, --ifReachableChk Check if network interfaces are reachable
-r, --vpnRoutesChk Check if >5 VPN routes are defined
-s, --vpnStatusChk Check if VPN client's status reports as 'Connected'
Global Flags:
-c, --config string config file (default is $HOME/.doxctl.yaml)
-v, --verbose Enable verbose output of commands
Tree - CLICK ME
$ doxctl vpn -i
NOTE: Using config file: /Users/smingolelli/.doxctl.yaml
┌─────────────────────────────────────────────────────────────────────────────────────────────┐
│ Interfaces Reachable Checks │
├────────────────────────────────────────────────────┬────────────────────────────────┬───────┤
│ PROPERTY DESCRIPTION │ VALUE │ NOTES │
├────────────────────────────────────────────────────┼────────────────────────────────┼───────┤
│ How many network interfaces found? │ 1 │ [en0] │
│ At least 1 interface's a utun device? │ false │ [] │
│ All active interfaces are reporting as reachable? │ true │ │
└────────────────────────────────────────────────────┴────────────────────────────────┴───────┘
WARNING:
Your VPN client does not appear to be defining a TUN interface properly,
your VPN is either not connected or it's misconfigured!
$ doxctl vpn -i
NOTE: Using config file: /Users/smingolelli/.doxctl.yaml
┌───────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Interfaces Reachable Checks │
├────────────────────────────────────────────────────┬────────────────────────────────┬─────────────┤
│ PROPERTY DESCRIPTION │ VALUE │ NOTES │
├────────────────────────────────────────────────────┼────────────────────────────────┼─────────────┤
│ How many network interfaces found? │ 2 │ [en0 utun2] │
│ At least 1 interface's a utun device? │ true │ [utun2] │
│ All active interfaces are reporting as reachable? │ true │ │
└────────────────────────────────────────────────────┴────────────────────────────────┴─────────────┘
Tree - CLICK ME
$ doxctl vpn -r
NOTE: Using config file: /Users/smingolelli/.doxctl.yaml
┌─────────────────────────────────────────────────────────────────────────────────────────────┐
│ VPN Interface Route Checks │
├────────────────────────────────────────────────────┬────────────────────────────────┬───────┤
│ PROPERTY DESCRIPTION │ VALUE │ NOTES │
├────────────────────────────────────────────────────┼────────────────────────────────┼───────┤
│ At least [5] routes using interface [NIL]? │ false │ 0 │
└────────────────────────────────────────────────────┴────────────────────────────────┴───────┘
WARNING:
Your VPN client does not appear to be defining a TUN interface properly,
it's either not connected or it's misconfigured!
$ doxctl vpn -r
NOTE: Using config file: /Users/smingolelli/.doxctl.yaml
┌─────────────────────────────────────────────────────────────────────────────────────────────┐
│ VPN Interface Route Checks │
├────────────────────────────────────────────────────┬────────────────────────────────┬───────┤
│ PROPERTY DESCRIPTION │ VALUE │ NOTES │
├────────────────────────────────────────────────────┼────────────────────────────────┼───────┤
│ At least [5] routes using interface [utun2]? │ true │ 148 │
└────────────────────────────────────────────────────┴────────────────────────────────┴───────┘
Tree - CLICK ME
$ doxctl vpn -s
NOTE: Using config file: /Users/smingolelli/.doxctl.yaml
┌───────────────────────────────────────────────────────────────────────────────────────────────┐
│ VPN Connection Status Checks │
├──────────────────────────────────────────────────────┬────────────────────────────────┬───────┤
│ PROPERTY DESCRIPTION │ VALUE │ NOTES │
├──────────────────────────────────────────────────────┼────────────────────────────────┼───────┤
│ VPN Client reports connection status as 'Connected'? │ false │ │
└──────────────────────────────────────────────────────┴────────────────────────────────┴───────┘
WARNING:
Your VPN client's does not appear to be a state of 'connected',
it's either down or misconfigured!"
$ doxctl vpn -s
NOTE: Using config file: /Users/smingolelli/.doxctl.yaml
┌───────────────────────────────────────────────────────────────────────────────────────────────┐
│ VPN Connection Status Checks │
├──────────────────────────────────────────────────────┬────────────────────────────────┬───────┤
│ PROPERTY DESCRIPTION │ VALUE │ NOTES │
├──────────────────────────────────────────────────────┼────────────────────────────────┼───────┤
│ VPN Client reports connection status as 'Connected'? │ true │ │
└──────────────────────────────────────────────────────┴────────────────────────────────┴───────┘
$ doxctl svrs -h
doxctl's 'svrs' subcommand can help triage & test connectivity to 'well known servers'
thru a VPN connection to servers which have been defined in your '.doxctl.yaml'
configuration file.
Usage:
doxctl svrs [flags]
Flags:
-a, --allChk Run all the checks in this subcommand module
-h, --help help for svrs
-s, --svrsReachableChk Check if well known servers are reachable
Global Flags:
-c, --config string config file (default is $HOME/.doxctl.yaml)
-v, --verbose Enable verbose output of commands
Tree - CLICK ME
$ doxctl svrs -s
NOTE: Using config file: /Users/smingolelli/.doxctl.yaml
INFO: Attempting to ping all well known servers, this may take a few...
--- Working through svc: openshift
--- Working through svc: elastic
--- Working through svc: idm
...one sec, preparing `ping` results...
WARNING: More than 5 hosts appear to be unreachable, aborting remainder....
┌─────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Well known Servers Reachable Checks │
├──────────────────────────────────────────┬──────────────────────┬────────────┬──────────────────┤
│ HOST │ SERVICE │ REACHABLE? │ PING PERFORMANCE │
├──────────────────────────────────────────┼──────────────────────┼────────────┼──────────────────┤
│ ocp-master-01a.lab1.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01a.rdu1.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01a.dfw1.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01a.lax2.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01a.jfk1.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01b.lab1.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01b.rdu1.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01b.dfw1.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01b.lax2.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01b.jfk1.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01c.lab1.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01c.rdu1.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01c.dfw1.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01c.lax2.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01c.jfk1.somedom.local │ openshift │ false │ N/A │
│ ocp-master-01a.lhr1.somedom.us │ openshift │ false │ N/A │
│ ocp-master-01a.fra1.somedom.us │ openshift │ false │ N/A │
│ ocp-master-01b.lhr1.somedom.us │ openshift │ false │ N/A │
│ ocp-master-01b.fra1.somedom.us │ openshift │ false │ N/A │
│ ocp-master-01c.lhr1.somedom.us │ openshift │ false │ N/A │
│ ocp-master-01c.fra1.somedom.us │ openshift │ false │ N/A │
├──────────────────────────────────────────┼──────────────────────┼────────────┼──────────────────┤
│ es-master-01a.lab1.somedom.local │ elastic │ false │ N/A │
│ es-master-01a.rdu1.somedom.local │ elastic │ false │ N/A │
│ es-master-01b.lab1.somedom.local │ elastic │ false │ N/A │
│ es-master-01b.rdu1.somedom.local │ elastic │ false │ N/A │
│ es-master-01c.lab1.somedom.local │ elastic │ false │ N/A │
│ es-master-01c.rdu1.somedom.local │ elastic │ false │ N/A │
├──────────────────────────────────────────┼──────────────────────┼────────────┼──────────────────┤
│ idm-01a.lab1.somedom.local │ idm │ false │ N/A │
│ idm-01a.rdu1.somedom.local │ idm │ false │ N/A │
│ idm-01a.dfw1.somedom.local │ idm │ false │ N/A │
│ idm-01a.lax2.somedom.local │ idm │ false │ N/A │
│ idm-01a.jfk1.somedom.local │ idm │ false │ N/A │
│ idm-01b.lab1.somedom.local │ idm │ false │ N/A │
│ idm-01b.rdu1.somedom.local │ idm │ false │ N/A │
│ idm-01b.dfw1.somedom.local │ idm │ false │ N/A │
│ idm-01b.lax2.somedom.local │ idm │ false │ N/A │
│ idm-01b.jfk1.somedom.local │ idm │ false │ N/A │
│ idm-01a.lhr1.somedom.us │ idm │ false │ N/A │
│ idm-01a.fra1.somedom.us │ idm │ false │ N/A │
│ idm-01b.lhr1.somedom.us │ idm │ false │ N/A │
│ idm-01b.fra1.somedom.us │ idm │ false │ N/A │
└──────────────────────────────────────────┴──────────────────────┴────────────┴──────────────────┘
WARNING:
Your VPN client does not appear to be functioning properly, it's likely one or more of the following:
- Well known servers are unreachable via ping --- try running 'doxctl vpn -h'
- Servers are unresovlable in DNS --- try running 'doxctl dns -h'
- VPN client is otherwise misconfigured!
doxctl svrs -s
NOTE: Using config file: /Users/smingolelli/.doxctl.yaml
INFO: Attempting to ping all well known servers, this may take a few...
--- Working through svc: openshift
--- Working through svc: elastic
--- Working through svc: idm
...one sec, preparing `ping` results...
┌────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Well known Servers Reachable Checks │
├──────────────────────────────────────────┬──────────────────────┬────────────┬─────────────────────────┤
│ HOST │ SERVICE │ REACHABLE? │ PING PERFORMANCE │
├──────────────────────────────────────────┼──────────────────────┼────────────┼─────────────────────────┤
│ ocp-master-01a.lab1.somedom.local │ openshift │ true │ rnd-trp avg = 44.525ms │
│ ocp-master-01a.rdu1.somedom.local │ openshift │ true │ rnd-trp avg = 24.337ms │
│ ocp-master-01a.dfw1.somedom.local │ openshift │ true │ rnd-trp avg = 55.118ms │
│ ocp-master-01a.lax2.somedom.local │ openshift │ true │ rnd-trp avg = 97.183ms │
│ ocp-master-01a.jfk1.somedom.local │ openshift │ true │ rnd-trp avg = 36.187ms │
│ ocp-master-01b.lab1.somedom.local │ openshift │ true │ rnd-trp avg = 44.237ms │
│ ocp-master-01b.rdu1.somedom.local │ openshift │ true │ rnd-trp avg = 17.678ms │
│ ocp-master-01b.dfw1.somedom.local │ openshift │ true │ rnd-trp avg = 56.559ms │
│ ocp-master-01b.lax2.somedom.local │ openshift │ true │ rnd-trp avg = 96.493ms │
│ ocp-master-01b.jfk1.somedom.local │ openshift │ true │ rnd-trp avg = 43.273ms │
│ ocp-master-01c.lab1.somedom.local │ openshift │ true │ rnd-trp avg = 41.358ms │
│ ocp-master-01c.rdu1.somedom.local │ openshift │ true │ rnd-trp avg = 31.427ms │
│ ocp-master-01c.dfw1.somedom.local │ openshift │ true │ rnd-trp avg = 55.095ms │
│ ocp-master-01c.lax2.somedom.local │ openshift │ true │ rnd-trp avg = 103.423ms │
│ ocp-master-01c.jfk1.somedom.local │ openshift │ true │ rnd-trp avg = 37.22ms │
│ ocp-master-01a.lhr1.somedom.us │ openshift │ true │ rnd-trp avg = 133.023ms │
│ ocp-master-01a.fra1.somedom.us │ openshift │ true │ rnd-trp avg = 136.647ms │
│ ocp-master-01b.lhr1.somedom.us │ openshift │ true │ rnd-trp avg = 127.451ms │
│ ocp-master-01b.fra1.somedom.us │ openshift │ true │ rnd-trp avg = 139.85ms │
│ ocp-master-01c.lhr1.somedom.us │ openshift │ true │ rnd-trp avg = 132.362ms │
│ ocp-master-01c.fra1.somedom.us │ openshift │ true │ rnd-trp avg = 137.558ms │
├──────────────────────────────────────────┼──────────────────────┼────────────┼─────────────────────────┤
│ es-master-01a.lab1.somedom.local │ elastic │ true │ rnd-trp avg = 44.029ms │
│ es-master-01a.rdu1.somedom.local │ elastic │ true │ rnd-trp avg = 32.187ms │
│ es-master-01b.lab1.somedom.local │ elastic │ true │ rnd-trp avg = 48.833ms │
│ es-master-01b.rdu1.somedom.local │ elastic │ true │ rnd-trp avg = 22.477ms │
│ es-master-01c.lab1.somedom.local │ elastic │ true │ rnd-trp avg = 55.587ms │
│ es-master-01c.rdu1.somedom.local │ elastic │ true │ rnd-trp avg = 25.79ms │
├──────────────────────────────────────────┼──────────────────────┼────────────┼─────────────────────────┤
│ idm-01a.lab1.somedom.local │ idm │ true │ rnd-trp avg = 47.484ms │
│ idm-01a.rdu1.somedom.local │ idm │ true │ rnd-trp avg = 22.766ms │
│ idm-01a.dfw1.somedom.local │ idm │ true │ rnd-trp avg = 54.07ms │
│ idm-01a.lax2.somedom.local │ idm │ true │ rnd-trp avg = 94.755ms │
│ idm-01a.jfk1.somedom.local │ idm │ true │ rnd-trp avg = 36.26ms │
│ idm-01b.lab1.somedom.local │ idm │ true │ rnd-trp avg = 41.171ms │
│ idm-01b.rdu1.somedom.local │ idm │ true │ rnd-trp avg = 27.097ms │
│ idm-01b.dfw1.somedom.local │ idm │ true │ rnd-trp avg = 51.547ms │
│ idm-01b.lax2.somedom.local │ idm │ true │ rnd-trp avg = 94.203ms │
│ idm-01b.jfk1.somedom.local │ idm │ true │ rnd-trp avg = 36.956ms │
│ idm-01a.lhr1.somedom.us │ idm │ true │ rnd-trp avg = 145.853ms │
│ idm-01a.fra1.somedom.us │ idm │ true │ rnd-trp avg = 146.425ms │
│ idm-01b.lhr1.somedom.us │ idm │ true │ rnd-trp avg = 127.987ms │
│ idm-01b.fra1.somedom.us │ idm │ true │ rnd-trp avg = 135.593ms │
└──────────────────────────────────────────┴──────────────────────┴────────────┴─────────────────────────┘
All the CLI subcommands can make use of either the -v or the --verbose switch to gather further diagnostics which can be helpful when triaging connectivity issues.
Tree - CLICK ME
For example:
$ doxctl dns -r -v
+ printf '\n\nDNS Resolver Checks\n===================\n\n\n'
DNS Resolver Checks
===================
++ printf 'get State:/Network/Service/com.cisco.anyconnect/DNS\nd.show\n'
++ scutil
+ vpn_resolvers='<dictionary> {
DomainName : somedom.local
SearchDomains : <array> {
0 : somedom.local
}
SearchOrder : 1
ServerAddresses : <array> {
0 : 10.5.0.18
1 : 10.5.0.19
2 : 192.168.7.85
}
SupplementalMatchDomains : <array> {
0 :
1 : somedom.local
}
}'
+ column -t
+ echo '<dictionary> {
DomainName : somedom.local
SearchDomains : <array> {
0 : somedom.local
}
SearchOrder : 1
ServerAddresses : <array> {
0 : 10.5.0.18
1 : 10.5.0.19
2 : 192.168.7.85
}
SupplementalMatchDomains : <array> {
0 :
1 : somedom.local
}
}'
+ grep -q 'DomainName.*somedom.local'
+ echo 'DomainName set'
+ echo '<dictionary> {
DomainName : somedom.local
SearchDomains : <array> {
0 : somedom.local
}
SearchOrder : 1
ServerAddresses : <array> {
0 : 10.5.0.18
1 : 10.5.0.19
2 : 192.168.7.85
}
SupplementalMatchDomains : <array> {
0 :
1 : somedom.local
}
}'
+ grep -A1 SearchDomains
+ grep -qE '[0-1].*somedom'
+ echo 'SearchDomains set'
+ echo '<dictionary> {
DomainName : somedom.local
SearchDomains : <array> {
0 : somedom.local
}
SearchOrder : 1
ServerAddresses : <array> {
0 : 10.5.0.18
1 : 10.5.0.19
2 : 192.168.7.85
}
SupplementalMatchDomains : <array> {
0 :
1 : somedom.local
}
}'
+ grep -A3 ServerAddresses
+ grep -qE '[0-1].*10.5'
+ echo 'ServerAddresses set'
DomainName set
SearchDomains set
ServerAddresses set
+ [[ 1 -eq 1 ]]
+ set +x