NSLookup

Network Server-side dns nslookup domain resolver mx txt cname ns a-record

This tool processes your data on the server: whatever you submit here is sent over the network to be processed, then the result is sent back to your browser.

What it does

Looks up the DNS records for a domain from the server, using a DNS resolver of your choice. Unlike your browser's own DNS cache (which may be stale, filtered, or hijacked by your ISP/router), this tool sends the query directly to a public resolver so you see the record exactly as that server returns it.

Try it

How it works

Your browser sends the domain, record type, and chosen resolver IP to /api/tools/nslookup.
The server (tools/nslookup/server.js) creates a dedicated dns.Resolver instance, points it at the chosen DNS server with setServers(), and performs the query using Node's native DNS resolution (resolve4, resolve6, resolveMx, resolveTxt, resolveNs, resolveCname, or resolveSoa).
The raw records are returned as JSON and rendered in the table above.

Why choose the DNS server?

Different resolvers can return different results for the same domain, especially for:

Geo-DNS / CDN records — a domain behind Cloudflare, Akamai, or a similar CDN, may return a different A record depending on which resolver (and therefore which network location) asks.
DNS propagation — after changing a DNS record, some resolvers refresh faster than others because of differing TTL caching behavior.
Filtering/censorship — some ISP resolvers rewrite or block certain domains; comparing against a major public resolver like Google or Cloudflare quickly reveals this.

Notes

System default uses whatever DNS resolver is configured on the server hosting PiliBox — this is not your own computer's resolver, since the lookup happens server-side.
SOA and NS queries ignore the record type filter subtlety and always return their respective record shape.
If the domain does not have the requested record type, an empty result (or a NXDOMAIN/ENODATA error) is shown rather than a fake empty success.