- Why DNS → name space and labels → domains, FQDN/PQDN → name servers → recursive vs. iterative resolution.
- DNS = the Internet’s directory: a client-server app that maps host NAMES → IP addresses (name resolution).
- People remember names; the network only understands numbers.
🎯 How this can come up · 2 questions
Mapping a host name to its IP address is called:
Correct: Name resolution.
DNS is a client-server application.
True.
- Names are hierarchical: labels on a tree with the root at the top.
- Siblings must have different labels → every full name is unique.
- IANA controls the top parts (com, sa, …); each organisation manages the rest → decentralized.
🎯 How this can come up · 1 question
Children of the same node in the DNS tree must:
Correct: Have different labels.
- Generic top-level domains; country domains (sa, us, jp…) are the other kind.
🎯 How this can come up · 1 question
The generic label for nonprofit organizations is:
Correct: org.
- Domain = a subtree under ONE administrative authority. Leaves have no subdomains (a host or a whole company).
- A domain’s name is the name of the node at the top of its subtree.
- Read from the leaf UP: aComputer → bDept → topUniversity → edu → root (the final dot).
🎯 How this can come up · 1 question
In the name sales.mcgraw.com., the top-level domain is:
Correct: com.
- FQDN = complete, ends with a dot, can be resolved. PQDN = partial; the resolver adds the local suffix.
🎯 How this can come up · 2 questions
Which name can be mapped directly to an IP address?
Correct: FQDN.
A PQDN is completed by the resolver on the client.
True.
- One central DNS server would be overloaded, a single point of failure, and hard to maintain.
- So DNS is a DISTRIBUTED database of hierarchical name servers.
🎯 How this can come up · 1 question
Why isn’t the DNS database stored on one central server?
It would get heavy traffic from all over the world, its failure would make every name unavailable, and it would be hard to maintain. DNS is a distributed, hierarchical database spread over many name servers.
- Each server knows about all the names below it.
- Primary: loads its data from its own disk file. Secondary: copies it from the primary → zone transfer.
🎯 How this can come up · 1 question
A secondary DNS server downloading data from the primary is called:
Correct: Zone transfer.
- Root servers point to the top-level-domain servers. There are 13 (named A–M).
🎯 How this can come up · 1 question
How many root servers are there in the slides?
Correct: 13.
- Caching: servers remember recent answers so the next lookup skips the search.
- App gives the name to the DNS client (resolver) → query → response → IP address back to the app.
- Client part = resolver. Server part = name server.
- Recursive: each server that doesn’t know asks the NEXT server itself, and the answer travels back down the same chain.
- 1–4: the query is passed along from server to server. 5–8: the answer comes back along the same chain.
- Each server in the chain asks the next one on the host’s behalf.
🎯 How this can come up · 1 question
In RECURSIVE resolution for sales.mcgraw.com from lab.CS.PSU.EDU.SA, who contacts DNS.com?
The root name server. In recursive resolution the local server asks the root, the root asks DNS.com, and DNS.com asks DNS.McGraw.com; the answer then flows back through each of them to the host.
- Iterative: a server that doesn’t know REPLIES with the address of the next server, and the LOCAL server does all the asking itself.
🎯 How this can come up · 2 questions
In iterative resolution, the root server answers the local server with:
Correct: The IP address of the next name server to ask.
Compare recursive and iterative DNS resolution.
Recursive: each server that lacks the answer queries the next server itself, and the answer is passed back along the same chain. Iterative: a server that lacks the answer replies with the address of the next server to ask, and the local name server sends each query itself until it gets the mapping, then answers the host.
- All the arrows start or end at the LOCAL server DNS.PSU.EDU.SA.
- Count: the local server sends three queries (root, DNS.com, DNS.McGraw.com).
🎯 How this can come up · 1 question
In the iterative example, which server sends the query to DNS.McGraw.com?
Correct: DNS.PSU.EDU.SA (the local server).
- DNS uses UDP or TCP on well-known port 53 (UDP for normal queries).
Seen again
🎯 How this can come up · 1 question
DNS uses well-known port:
Correct: 53.
No slides match this filter.








