A site is down and you want to know whether it is DNS or the server. An email is bouncing and you suspect the MX records are wrong. You just changed a domain's nameservers and you want to confirm the change has propagated. All three of these are DNS questions, and all three are answerable in seconds from your phone — no laptop, no dig command, no shell.
This guide covers what a DNS lookup actually returns, what each record type means in plain terms, and how to query any domain from Android.
What DNS Lookup Really Does
DNS is the phone book of the internet: it translates a name people can remember (example.com) into the addresses and metadata machines need. A DNS lookup is you asking a resolver, "what does this domain point to?" The answer comes back as a set of records, each a different type for a different purpose.
When you load a website, your device does this lookup automatically and silently. A DNS tool just lets you do it deliberately, see the raw answer, and pick which record type you want — which is exactly what you need when something is broken or you are setting something up.
The Record Types You Actually Care About
Most DNS troubleshooting comes down to a handful of record types:
- A record — maps a domain to an IPv4 address. The most common lookup. If a site is unreachable, the A record is the first thing to check: does the domain resolve to the IP you expect?
- AAAA record — the same idea for IPv6. Increasingly relevant as networks go dual-stack.
- CNAME — an alias pointing one name at another. Common for pointing at the root domain, or a custom domain pointing at a hosting provider.text
www - MX record — mail exchanger. This is where email for the domain is delivered. If mail is bouncing, the MX records tell you which servers are supposed to accept it and in what priority order.
- TXT record — free-form text, used for SPF, DKIM, domain verification, and DMARC. If email is landing in spam or a service verification is failing, the TXT records are usually the cause.
- NS record — the authoritative nameservers for the domain. When you move a domain between registrars or DNS providers, you check NS records to confirm the change took effect.
How to Run a DNS Lookup From Your Phone
With Network Toolkit, the flow is:
- Open the DNS tool.
- Type the domain you want to query — , notext
example.comneeded.texthttp:// - Pick the record type, or query the common set at once.
- Read the answer. A and AAAA show IP addresses; MX shows mail servers with priorities; TXT shows the raw text strings; NS shows the nameservers.
Because the query goes straight to a public resolver, you get the live answer the rest of the internet sees, not a stale cached copy from one device.
Reading the Results in Real Situations
"Is the site down, or is it me?" Look up the A record. If it returns the IP you expect, DNS is fine and the problem is the server or the route to it — try a ping or traceroute to that IP next. If the A record is missing or wrong, the problem is DNS itself.
"Email to this domain keeps bouncing." Look up the MX records. No MX records, or MX pointing at a server that no longer exists, explains the bounce. The priority numbers tell you the intended order — lower number is tried first.
"I added an SPF/verification record but the service says it cannot find it." Look up the TXT records and confirm the exact string is present. DNS changes are not instant; if you just added it, propagation can take anywhere from minutes to a day depending on the record's TTL.
"I changed nameservers — did it work?" Look up the NS records. If they still show the old provider, the change has not propagated yet. Check again later.
Why Propagation Takes Time
DNS answers are cached at every level — your phone, your network's resolver, intermediate resolvers — for a duration set by each record's TTL (time to live). When you change a record, caches that already hold the old value keep serving it until the TTL expires. This is why a change can look live from one network and stale from another. Querying directly from your phone, on mobile data versus Wi-Fi, can even show you two different cached states, which is a useful way to gauge how far a change has spread.
Why Do This on a Phone
DNS problems do not wait for you to be at a desk. A site goes down, mail starts bouncing, or a deploy needs a DNS confirmation while you are away from your computer. Having the lookup in your pocket means you can diagnose the difference between a DNS issue and a server issue immediately, decide whether to wait for propagation or escalate, and do it all from the device you already have in your hand.
Pair the DNS tool with ping and traceroute — resolve the name, confirm the IP, then test whether that IP is reachable — and you can triage most "the internet is broken" situations end to end without ever opening a laptop.