Network 7 min read 1,591 words By LaiUse Editorial Team Reviewed 28 October 2026

DNS Lookup — Complete Guide

DNS Lookup performs a DNS lookup for a domain name and returns information for the selected DNS record type.

What it does

The tool performs a DNS lookup for a domain name and returns information for the selected DNS record type. It is designed for single, interactive queries: enter a name, choose one of the supported record types, run the lookup, and inspect the result. The supported choices are A, AAAA, CNAME, MX, NS, PTR, SOA, and TXT. These record types cover common DNS needs, including IPv4 and IPv6 addresses, aliases, mail exchange information, name servers, reverse records, zone authority information, and text records.

Although the interface performs local processing, the DNS resolution is not completed entirely in the browser. The lookup calls the backend endpoint /api/tools/dns-lookup?domain=${encodeURIComponent(cleanDomain)}&type=${encodeURIComponent(recordType)}, so the domain name and selected record type are included in a request to the service. The implementation also calls /tools/${tool.slug}/use. Results are not updated live while typing; a lookup must be submitted, and changing the input or record type requires another submission. The tool includes a built-in example using example.com and can copy the resulting information to the clipboard.

When to use it

How to use it

  1. Locate the field labeled Domain Name. The field accepts a hostname such as example.com. The tool does not accept a file containing names; each query is based on text you paste or type.
  2. Enter the domain name, or use the built-in example value, example.com. Remove any surrounding whitespace before submitting the lookup because the tool cleans the entered value before sending it to the DNS endpoint.
  3. Locate the field labeled Record Type and choose the DNS record information you want. The available values are A, AAAA, CNAME, MX, NS, PTR, SOA, and TXT.
  4. Activate the tool’s lookup or submit action. The tool does not publish a separate button label, so there is no additional exact wording to reproduce. The lookup does not run automatically as you type.
  5. Wait for the request to complete. The browser sends the cleaned domain name and selected record type to the backend DNS lookup endpoint. A successful result contains the DNS information returned for that combination of domain and record type.
  6. Review the displayed result. If you need to retain it, use the tool’s copy-to-clipboard capability to copy the available output. If you change the domain or record type, run the lookup again rather than expecting the current result to refresh automatically.

Worked example

Suppose you want to see the IPv4 records for the built-in example domain. Enter example.com in the field labeled Domain Name. Open the Record Type choice and select A, then activate the lookup action. Because the tool does not auto-run, pressing the action is required to send the request.

The expected successful output is the DNS A-record answer for example.com: information identifying the queried domain together with the IPv4 address data returned by DNS for it. A domain can legitimately have more than one A record, so the result may contain multiple addresses. The tool does not define a fixed output layout, a fixed set of records, or a guaranteed current IP address, and the address for example.com should not be assumed to remain constant.

For a different check, select MX instead and run the lookup again. The new result should describe the mail exchange records published for the same domain. Switching from A to MX does not transform the previous result; it starts a new backend request using the newly selected record type. You can then copy the displayed information if it is needed elsewhere.

Limitations and edge cases

Troubleshooting

Frequently asked questions

Does the tool perform the DNS lookup entirely in the browser? No. The interface performs local processing, but the lookup itself calls a backend endpoint. The domain and record type are sent in the lookup request, so this should not be described as a completely offline or entirely browser-only DNS resolver.

Which DNS record types can I select? The available choices are A, AAAA, CNAME, MX, NS, PTR, SOA, and TXT. Select one of these in Record Type before running the lookup.

Can I upload a DNS zone file or a list of domains? No. There is no file input, and the tool cannot open, upload, or read local files. It operates on a domain name that you paste or type.

Does the result update while I type? No. The tool does not auto-run and does not provide live output. Submit the lookup after entering the domain and choosing the record type; run it again whenever either value changes.

Can I download the lookup result? No. The tool can copy the available result to the clipboard, but it has no file-download capability. Use a separate application to save copied output if you need a local record.

Is there a published maximum number of records or a maximum domain length? No numeric limit is published. Do not infer a specific limit from the interface, and use a different service if you need documented bounds for automated or high-volume work.

Will the result always contain the same DNS records? No. DNS information can change between queries. The result represents the data returned by the backend lookup at the time the request completes, and a domain may have multiple records for some record types.

Does the tool save my previous query? No. It does not use local storage and does not remember state between visits. Copy any result you need before leaving the page.

When is a different DNS tool better? Use a command-line resolver or specialized DNS utility for scripted comparisons, extensive record inventories, delegation tracing, DNSSEC inspection, batch processing, or detailed network diagnosis. This tool is best suited to a quick, interactive lookup for one domain and one selected record type.

Want to try it? Open the DNS Lookup — it runs in your browser, so your files stay on your device.

Browse every guide · Read the blog · About LaiUse