INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

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.

Prerequisite

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

One service, different identifier scopes
IdentifierFictional exampleObject and scope
DNS namedocs.exampleA name used to look up DNS information, not a physical-device count.
IP address192.0.2.20A destination specified at the IP layer. IPv6 addresses are assigned to interfaces.
MAC address00:00:5e:00:53:01A destination used on an Ethernet link, distinct from a remote service name.
Transport portTCP/443A 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.

Two address values for a name, not a diagram of two devices
Two address values for a name, not a diagram of two devices1: Name docs.example — Fictional mapping — IPv4 192.0.2.20. 2: Name docs.example — Fictional mapping — IPv4 192.0.2.2112Name docs.exampleIPv4 192.0.2.20IPv4 192.0.2.21Two address values for a name, not a diagram of two devices1: Name docs.example — Fictional mapping — IPv4 192.0.2.20. 2: Name docs.example — Fictional mapping — IPv4 192.0.2.2112Namedocs.exampleIPv4 192.0.2.20IPv4 192.0.2.21
  1. Name docs.example → IPv4 192.0.2.20Fictional mapping
  2. 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.

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.

A list contains two IPv6 addresses. What is the physical-device count?
Read the answer and reason

Answer: The address count alone does not determine it · We need interface assignment and topology information. Multiple addresses may belong to one interface.

In the IPv4/Ethernet example, whose MAC is the first frame’s destination?
Read the answer and reason

Answer: The selected next-hop router · The direct recipient is 192.0.2.1. Its MAC is the frame destination; 203.0.113.20 remains the packet destination.

Two records contain only “443”. Do they establish the same transport endpoint?
Read the answer and reason

Answer: No; IP and transport context are needed · Different IP addresses or transports can use the same port number. The number alone does not establish the same endpoint.

Check, then explain in your own words

  1. State the object and scope of each identifier.
  2. Explain why multiple IP addresses do not establish a device count.
  3. 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.