Name resolution - Learn Tech From Zero

2.2 Given a scenario, configure servers to use network infrastructure services.

📘CompTIA Server+ (SK0-005)

Name resolution is the process of translating human-friendly names (like server01.company.local) into IP addresses (like 192.168.1.10) so that computers and applications can communicate over a network. Computers cannot use names directly; they need IP addresses.

There are three main methods for name resolution in a server/network environment:

1. Domain Name Service (DNS)

DNS is the most common method for name resolution in networks, especially in enterprise IT environments.

What it is: DNS is a service (and a database) that translates domain names into IP addresses. Think of it as the network’s “phone book” for servers and devices.
How it works in IT:
1. A client wants to reach a server called fileserver.company.local.
2. The client asks a DNS server: “What is the IP for fileserver.company.local?”
3. The DNS server responds with the IP, e.g., 10.10.20.5.
4. The client now communicates directly with that IP.
Key components:
- DNS Server: Stores DNS records and responds to queries.
- DNS Records: Map names to IP addresses. The most common records are:
  - A Record: Maps a hostname to an IPv4 address.
  - AAAA Record: Maps a hostname to an IPv6 address.
  - CNAME Record: Maps an alias name to another hostname.
  - PTR Record: Used for reverse DNS (IP to name resolution).
Example in an IT environment:
In an office network, the IT team can set up a DNS server so that employees can access intranet.company.local without knowing the IP address. If the server’s IP changes, updating the DNS keeps all clients working without reconfiguring them.
Exam tip: Understand that DNS is hierarchical: root → top-level domain (TLD) → domain → subdomain → host.

2. Fully Qualified Domain Name (FQDN)

FQDN is the complete address of a device in the domain namespace.

Definition: A Fully Qualified Domain Name includes both the hostname and the domain name, ending with the top-level domain.
Structure: hostname.subdomain.domain.tld Example: webserver.sales.company.local
- webserver → hostname (specific server)
- sales → subdomain
- company → main domain
- local → top-level domain (TLD) in a private network
Why it matters in IT:
- Using FQDN ensures there is no ambiguity when connecting to servers.
- Critical for services like email servers, web servers, and database servers, which rely on precise names.
- Many enterprise applications and authentication services (like Active Directory) require FQDNs.
Exam tip: Know the difference between a hostname (webserver) and FQDN (webserver.sales.company.local).

3. Hosts File

The hosts file is a local file on a computer that maps hostnames to IP addresses.

Location:
- Windows: C:\Windows\System32\drivers\etc\hosts
- Linux/Unix: /etc/hosts
How it works:
1. When a client tries to resolve a hostname, it first checks the hosts file.
2. If the name is found, it uses that IP directly.
3. If not, it queries DNS.
Format: 192.168.1.10 fileserver.company.local
192.168.1.11 dbserver.company.local
Use cases in IT:
- Temporary overrides when DNS is not yet configured.
- Testing new server setups without updating DNS.
- Small networks without a DNS server.
Exam tip: Remember that hosts file overrides DNS. If an entry exists in the hosts file, the system will not query DNS for that hostname.

Key Differences: DNS vs Hosts File vs FQDN

Feature	DNS	Hosts File	FQDN
Location	Network server	Local computer	Part of a name system
Scale	Global or enterprise-wide	Single device	Global uniqueness in domain
Dynamic Updates	Yes (can be automated)	No (manual edit)	N/A
Use in IT Environment	Access shared servers across network	Temporary fixes or small setups	Identify exact server location

Summary for the Exam

Name resolution converts hostnames to IP addresses.
DNS is the central system used in networks to resolve names dynamically.
FQDN is the complete, unique network address of a device.
Hosts file is a local, manual mapping for name resolution.
Order of resolution in most OS: Hosts file → DNS → other methods (like NetBIOS or WINS in Windows).

Tip: You may get scenario-based questions asking how a client resolves a server name or which method is used when DNS fails. Always remember hosts file overrides DNS, and FQDN specifies the exact server.