Networking: DNS (Domain Name System)
What It Does
DNS translates human-readable names (like a hostname or domain name) into the numeric IP addresses (IPv4 or IPv6) that devices actually use to find each other on a network — often described as "the phonebook of the internet." It runs primarily over UDP port 53, falling back to TCP only for responses too large for a single UDP packet (e.g., certain DNSSEC-signed answers) or for zone transfers between DNS servers.
How a Lookup Works
A typical DNS lookup follows a hierarchical process: a device first checks its local cache for a previously-resolved answer; if not found, the query goes to a recursive resolver (often run by an ISP or organization's IT department), which in turn queries a root server, then a top-level-domain (TLD) server, and finally the authoritative server that holds the actual, definitive record for that specific name — which returns the answer, typically all within milliseconds. Every DNS record carries a TTL (Time to Live), in seconds, telling resolvers how long they're allowed to cache the answer before asking again — this is the mechanism behind "DNS propagation delay": a changed record isn't visible everywhere instantly, it becomes visible as each resolver's cached copy expires according to its TTL.
Common Record Types
Not every DNS lookup returns an IP address — DNS is a general-purpose name-to-value lookup system with several record types, the most relevant being:
- A — maps a name to an IPv4 address (the most common record type).
- AAAA — maps a name to an IPv6 address.
- CNAME (Canonical Name) — an alias pointing one name at another name (not directly at an address); the resolver follows the CNAME and then looks up that name's own A/AAAA record.
- PTR (Pointer) — the reverse of an A record: given an IP address, returns the associated hostname ("reverse DNS"). Used by some logging/security tools to display a hostname next to a connecting IP, and a common source of confusion when a PTR record is missing, misconfigured, or simply doesn't match the forward A record (nothing requires forward and reverse records to agree).
- MX (Mail Exchanger) — directs email for a domain to the correct mail server(s), with a priority value for failover order.
- SRV (Service) — advertises the hostname and port for a specific service, letting a client discover both in one lookup rather than needing a hardcoded port; used by some enterprise/directory protocols.
- TXT — arbitrary text data attached to a name, commonly used today for email-sender-verification schemes (SPF/DKIM/DMARC) and domain-ownership verification, rather than for anything client devices query directly.
Common Misunderstandings
- "If I can ping an IP but not the hostname, the network is down" — usually the opposite conclusion is right: successfully pinging the IP address directly proves the network path is fine, and the failure is isolated to name resolution specifically — check the DNS server configuration and reachability, not the network path.
- "DNS changes take effect immediately everywhere" — no; each resolver caches a record until its TTL expires, so a change can take anywhere from seconds to (for long-TTL records) many hours to be visible from a given location, and different resolvers will show the old vs. new answer simultaneously during that window.
- "A working forward (A) record guarantees a working reverse (PTR) record, or vice versa" — the two are configured independently and can disagree or one can simply be missing; don't assume a hostname showing up in a log via reverse DNS is authoritative proof of anything beyond "someone configured a PTR record that says so."
Troubleshooting Tools
- nslookup / dig — query DNS directly and see exactly what a given resolver returns for a name, bypassing application-level caching to isolate whether a problem is DNS itself or something downstream.
- ipconfig /flushdns (Windows) — clears the local resolver cache, useful after a DNS record change to rule out "I'm still seeing the old answer because my own machine cached it."
Related Pages
- Networking: IPv4
- Networking: IPv6
- Networking: DHCP
- Networking: UDP
- IP Networking in Two-Way Radio Systems
- Port Forwarding and Remote Access
- IANA
References
See also: CTI product documentation
This article is part of the CTI Products Knowledge Base. Questions about RadioPro or MCN products? Call +1 (513) 595-5900 or email info@ctiproducts.com.
Informational only. This article is general background and is not engineering, safety, legal or regulatory advice. Verify requirements with the equipment manufacturer and the applicable authority before relying on it. Product names and trademarks belong to their respective owners.