You can also try a different command like "ping." However, the ping command relies on your computer's cached DNS routing information, so it's a bit less accurate. If you wanted to try using ping, you could type "ping YourDomainName.org" into the console and you would get something like this:
$ ping YourDomainName.org
PING YourDomainName.org (220.127.116.11): 56 data bytes 64 bytes from 18.104.22.168: icmp_seq=0 ttl=56 time=24.972 ms 64 bytes from 22.214.171.124: icmp_seq=1 ttl=56 time=31.198 ms Request timeout for icmp_seq 2 64 bytes from 126.96.36.199: icmp_seq=3 ttl=56 time=28.417 ms
(The connection will keep pinging until you stop it--you can use ctrl-c to cancel.)
The reason I'm using dig is because I can query the specific server, rather than relying on cached data in my computer.
To start, you can type "dig" and the domain you want to query. The command would look like this:
$ dig YourDomainName.org
However, at this point, this would still get you a DNS response based on what your local computer is caching.
But! you can make it more specific by adding in the server hosting the domain.
To find the server hosting the domain, you can do a whois lookup within the console by typing the command "whois YourDomainName.org". A lot of data spits out, but eventually toward the bottom, you will see Name Server listings.
So, using dig, you can include this server information in your command. You'll type "dig YourDomainName.org @servername". So, in our case, in the command line you would have either