Troubleshoot and test DNS lookups

You can use tools such as nslookup to troubleshoot and test the DNS.


To test specific records in Glesys DNS, you can use the nslookup tool, which is available on Linux, macOS, and Microsoft Windows.

When starting the tool, you first set the DNS server to one of Glesys's DNS servers. This ensures that the data you query is fresh and not cached by another DNS server. You specify the server using the server keyword.

If you want to test whether the DNS works end-to-end (i.e., that DNS servers on the internet are resolving queries to Glesys's DNS servers for your domain), you set the server to, for example, Google's DNS.

You change the record type using set type=TYPE.

First, start the nslookup tool:

Command
nslookup

Now you can enter commands and look up hostnames at the > prompt.

Example nslookup session. Commands are highlighted.
> server ns1.namesystem.se
Default server: ns1.namesystem.se
Address: 195.238.76.18#53
Default server: ns1.namesystem.se
Address: 2a02:750:aaaa::1#53
> set type=A
> example.com
Server:         ns1.namesystem.se
Address:        195.238.76.18#53

Name:   example.com
Address: 203.0.113.99
> exit

To look up the MX records for the domain example.com, use set type=MX. First, let's start nslookup again.

Performing lookups from an external DNS

Here, we perform a lookup using Google's DNS. If everything is configured correctly, Google's DNS should query Glesys DNS for the information.

Start the nslookup tool again:

If it doesn’t work, try querying the NS records to check if they point to Glesys DNS servers.

Last updated

Was this helpful?