Names, addresses, and ports

A street address tells a delivery service where to go. It does not identify the department that should receive the parcel or decide whether the recipient may open it. Networking also separates several kinds of decision, although the postal analogy cannot capture caches, proxies, or changing routes.

The name is the starting point

Suppose a fictional browser opens library.example. A resolver helps obtain the requested DNS records. An A record contains an IPv4 address; an AAAA record contains an IPv6 address. Other types describe aliases, mail handling, or other information. DNS is a distributed database of typed records, not just one worldwide list of machines.

A resolver may already have an answer in its cache. Otherwise it can consult other DNS servers, following the naming hierarchy as needed. The authoritative service for a zone publishes its records; a recursive resolver helps clients obtain answers. These are roles, and one physical machine can perform more than one role.

An answer has context and a lifetime

A record’s time to live limits ordinary caching. Updating an authoritative record does not force every cached copy to disappear immediately. Different clients can temporarily use different addresses. Services can also intentionally return different answers for different locations or policies.

Therefore, record the name, record type, answer, time, and observation point when explaining a naming result. One address does not establish one physical server: load balancers and shared hosting can put many services behind it. Conversely, one service may use many addresses.

PredictThe library’s name resolves successfully, but a member cannot renew a book. Has DNS proved that the renewal service works?

No. DNS supplied naming information. A usable route, an accepting transport endpoint, a functioning application, and a permitted renewal are further questions. A correct first step does not establish the remaining steps.

Addresses and ports answer different questions

IP addressing helps network devices forward packets toward a destination. A route selects the next hop; DNS does not normally carry the later web request through its servers. The transport adds endpoint information. TCP and UDP each use port numbers, with separate namespaces. A destination address, transport, and port are more informative together than a port number alone.

TCP offers an ordered byte stream with retransmission and congestion control. UDP preserves datagram boundaries but does not itself guarantee delivery or ordering. Applications can add mechanisms above UDP; QUIC is one example. Neither a familiar port nor the use of TCP automatically provides encryption.

Finally, the application interprets the request

The library service reads an HTTP request and decides what it means. HTTPS protects the communication channel under TLS trust rules, while the application still decides which member may renew which book. A useful description keeps all four questions separate: What name was resolved? Where could packets travel? Which endpoint received them? What operation was permitted?