Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Following instruction on this page you can test if your host can resolve domain names (such as patientsknowbest.com) to an IP address.

On the machine that runs the service run below command:

nslookup my.patientsknowbest.com

The command will query a name server for our address. Which name server is picked depends on the confguration of your system/network.

TIP: Run:

  • nslookup my.patientsknowbest.com sonia.ns.cloudflare.com or

  • nslookup my.patientsknowbest.com shane.ns.cloudflare.com

to query one of the authorative nameserver for patientsknowbest.com.

Expected success output

Server:		127.0.0.53
Address:	127.0.0.53#53

Non-authoritative answer:
Name:	my.patientsknowbest.com
Address: 35.246.122.93

The Address: 35.246.122.93bit indicate that the domain name can can be resolved to an IP address.

TIP: Make sure the IP address (35.246.122.93 in this example) matches the IP listed for a given endpoint in our PKB API Network Connectivity page.

Expected failure outputs

Time out

nslookup my.patientsknowbest.com
;; communications error to 127.0.0.53#53: timed out

Indicates some sort of local DNS and/or network issue.

NEXT: Try running the same command on a different machine. If it works, then the problem is likely local to target host. Try to resolve the issue within your organization.

Missing record

Non-authoritative answer:
*** Can't find my.patientsknowbest.com: No answer

Indicates the absense of a corresponding DNS record for the queried name.

NEXT: Check if there is is a typo in the domain.

NEXT: Try running the same command on a different machine. If it works, then the problem is likely local to target host. Try to resolve the issue within your organization.

NEXT: Visit https://www.pkbstatus.com/ and look out comms from us.

Missing domain

** server can't find my.patientsknowbest.com: NXDOMAIN

Indicates that the patientsknowbest.com does not exists.

NEXT: Check if there is is a typo in the domain.

NEXT: Try running the same command on a different machine. If it works, then the problem is likely local to target host. Try to resolve the issue within your organization.

NEXT: Visit https://www.pkbstatus.com/ and look out comms from us.

  • No labels