Topic lessonTopic: networking foundations
Names, IP addresses, MAC addresses and ports: what each identifies
Names, IP addresses, MAC addresses and ports have different roles, even when they concern the same service. A name is a key for looking up information; an IP address specifies a network-layer destination; a MAC address serves delivery on a link; a port distinguishes a TCP or UDP endpoint. Read them separately in a fictional document-service example.
Distinguish four identifier scopes, avoid counting devices from address counts, and explain the difference between a remote destination IP and the destination MAC on the first link.
An interface is a point where a device attaches to a network. A link supports direct delivery to a neighbor. The examples are fixed, fictional data; no connections, commands or device information are required.
Ask what each destination field identifies
| Identifier | Fictional example | Object and scope |
|---|---|---|
| DNS name | docs.example | A name used to look up DNS information, not a physical-device count. |
| IP address | 192.0.2.20 | A destination specified at the IP layer. IPv6 addresses are assigned to interfaces. |
| MAC address | 00:00:5e:00:53:01 | A destination used on an Ethernet link, distinct from a remote service name. |
| Transport port | TCP/443 | A number interpreted with the IP address and TCP or UDP to distinguish an endpoint. |
For example, docs.example → 192.0.2.20 → TCP/443 lists destination information chosen for this lesson. It does not determine a MAC address. For that, we need to know the outgoing link and the next hop on it.
A name or an interface can have multiple IP addresses
A DNS A record carries an IPv4 address. One name can have multiple A records. Our fictional data gives docs.example two addresses: 192.0.2.20 and 192.0.2.21. This is not a measured DNS response.
- Name docs.example → IPv4 192.0.2.20Fictional mapping
- Name docs.example → IPv4 192.0.2.21Fictional mapping
- Name docs.example
- Fictional name
- IPv4 192.0.2.20
- Address value 1
- IPv4 192.0.2.21
- Address value 2
In IPv6, one interface can have multiple addresses. A fictional interface could have both 2001:db8:10::20 and 2001:db8:10::21. Seeing two IP addresses therefore does not establish two physical devices. Device topology requires additional information.
Separate the remote destination IP from the first-link destination MAC
This example sends IPv4 unicast traffic over Ethernet: traffic addressed to one destination, 203.0.113.20. The sender has already selected the router at 192.0.2.1 as its first next hop: the neighbor to receive the packet directly.
For this fictional example, assume no address rewriting, no packet encapsulation and no application-layer intermediary. Compare IP and MAC destination fields under those conditions.
- Sender 192.0.2.10 → Next hop 192.0.2.1First Ethernet delivery
- Next hop 192.0.2.1 → Remote target 203.0.113.20Remaining path omitted
- Sender 192.0.2.10
- Sends on the first link
- Next hop 192.0.2.1
- MAC 00:00:5e:00:53:01
- Remote target 203.0.113.20
- Further path omitted
| Field | Fictional value | Role |
|---|---|---|
| IPv4 packet destination | 203.0.113.20 | The remote destination specified in this example. |
| Ethernet frame destination | 00:00:5e:00:53:01 | The router receiving the frame on the first link. |
A frame is a unit delivered on a link. ARP (Address Resolution Protocol) resolves an IPv4 next-hop address, for example, to an Ethernet address. A cached mapping may be used, so a fresh query is not required for every packet. DNS is not how the sender finds the remote server’s MAC address.
Read a port with the IP address and transport
The number 443 alone does not specify a transport endpoint. TCP/443 and UDP/443 at 192.0.2.20 use different transports. A port is neither a device count nor a hardware serial number. The related TCP/UDP lesson explains message boundaries and listening in detail.
When describing a destination, ask which name, which IP, which link and next hop, and which transport and port are involved. Address values and registered port numbers alone do not certify a running or safe application.
Check the identifier scope in three situations
Choose an option to see the result and explanation.
Check, then explain in your own words
- State the object and scope of each identifier.
- Explain why multiple IP addresses do not establish a device count.
- Read the first-link destination IP and MAC separately.
Check your understanding: What should you ask first when reading a name, IP, MAC or port?
Ask what it identifies and within which scope.
A name or interface can have multiple IP addresses. A link next hop differs from a remote IP destination, and a port needs IP and transport context. Identifier values and counts do not by themselves establish device topology or application operation.
Sources and conditions checked
Primary references are collected here with their scope, conditions and corresponding sections. Independent expert review and live-environment validation have not been performed.
Scope and conditionsSection 3.4.1: IPv4 A records and multiple addresses; no DNS operation or complete updates audit.
Used in this lessonAsk what each destination field identifies A name or an interface can have multiple IP addresses Separate the remote destination IP from the first-link destination MAC
Scope and conditionsSections 2.1/2.2: interface assignment, multiple addresses and notation; the device-count boundary is an editorial inference.
Used in this lessonAsk what each destination field identifies A name or an interface can have multiple IP addresses
Scope and conditionsPacket Generation: selected next hop, Ethernet address resolution and cache; no routing algorithm or OS procedure.
Used in this lessonAsk what each destination field identifies Separate the remote destination IP from the first-link destination MAC
Scope and conditionsSections 3/3.1: neighbor link-layer address resolution and distinction from IPv4; no full message or security validation.
Used in this lessonSeparate the remote destination IP from the first-link destination MAC
Scope and conditionsSections 1/3: default recommendation against embedding stable link-layer addresses when autoconfiguring stable IPv6 addresses; not a universal address-generation rule.
Used in this lessonA name or an interface can have multiple IP addresses
Scope and conditionsSection 2.1.4: documentation unicast MAC range 00:00:5e:00:53:00–ff, checked in the text that obsoletes RFC7042.
Used in this lessonAsk what each destination field identifies
Scope and conditionsSections 2/3: 2001:db8::/32 documentation prefix, not a local-use configuration range.
Used in this lessonA name or an interface can have multiple IP addresses
Scope and conditionsSections 3/4: documentation blocks, including 192.0.2.0/24; not live targets or local configuration.
Used in this lessonAsk what each destination field identifies
- RFC 6761 — Example domainsChecked:
Scope and conditionsSection 6.5: reserved example names; APIs may resolve them normally, so this lesson initiates no lookup.
Used in this lessonAsk what each destination field identifies
Scope and conditionsRegistry Note: registration does not certify actual applications or benign traffic; no specific 443 assignment or observed traffic validation.
Used in this lessonAsk what each destination field identifies Read a port with the IP address and transport