The internet's naming system
The Domain Name System translates human-readable names into information computers use to reach services. When you enter a domain, a resolver finds records that can lead the browser to an IPv4 or IPv6 address.
DNS is distributed rather than stored in one global server. Root servers, top-level-domain servers, authoritative name servers, and recursive resolvers cooperate to answer questions.
How a lookup is resolved
Your device usually asks a recursive resolver operated by an internet provider, company, VPN, or chosen DNS service. If the answer is not cached, the resolver follows referrals through the DNS hierarchy until it reaches an authoritative source.
The answer includes a time to live, or TTL, that tells caches how long they may reuse it. Caching improves speed and reduces load, but it also means DNS changes can take time to appear everywhere.
Common record types
A records contain IPv4 addresses and AAAA records contain IPv6 addresses. CNAME records point one hostname to another name. MX records identify mail exchangers and include priorities.
NS records identify authoritative name servers. TXT records carry text used for domain verification, email authentication policies such as SPF and DMARC, and other machine-readable declarations.
DNS privacy and security
Traditional DNS queries can be visible to the local network and resolver. DNS over HTTPS and DNS over TLS encrypt the connection to the recursive resolver, but the resolver still processes the requested domain and must be trusted under its policy.
DNSSEC allows resolvers to validate cryptographic signatures and detect forged DNS data for signed zones. It authenticates records; it does not encrypt the query or hide the domain name.
Troubleshooting DNS
When a domain fails, check whether authoritative name servers respond, whether the expected record exists, and whether recent changes are still cached. A missing record type can be normal—for example, a domain may use only IPv4 and have no AAAA record.
DNS tools reveal published configuration, not private server data. IPMora requests six common record types and does not store the submitted domain or result.