OSNTC.006: DNS Basics

Black and neon-green DNS Basics cover showing a laptop resolving a domain name through a DNS server to a web server

DNS stands for Domain Name System. Its basic job is to help devices turn easy-to-remember names such as example.com into IP addresses that computers can use to communicate.

This lesson follows OSNTC.005: DHCP Basics. DHCP can give a device its network settings, including DNS-server addresses. DNS then helps that device find services by name.

Names and IP Addresses

People usually remember names better than long numeric addresses. DNS connects those two ideas. You enter a name; a DNS lookup can return the IP address associated with that name.

A Simple DNS Lookup

  1. You enter a domain name.
  2. Your device asks its configured DNS resolver for an answer.
  3. The DNS system finds or retrieves the appropriate record.
  4. The resolver returns the answer to your device.
  5. Your device can then contact the destination using the returned address.

Video: How DNS Works

This PowerCert Animated Videos lesson gives a beginner-friendly visual explanation of DNS resolution, including resolvers, root servers, domain servers, and authoritative name servers.

DNS Resolver

A DNS resolver is the DNS server your device asks for help. Your laptop, phone, server, or mining-management computer may receive the resolver address automatically through DHCP or use one that was configured manually.

A and AAAA Records

An A record maps a name to an IPv4 address. An AAAA record maps a name to an IPv6 address. There are many other DNS record types, but these two make the basic name-to-address idea easy to see.

Test DNS With nslookup

nslookup example.com

nslookup can ask DNS for information about a name. A technician can use it to separate a name-resolution problem from a more general network-connectivity problem.

Simple Troubleshooting Example

Imagine a computer can reach its default gateway but a website name will not resolve. Check the computer’s DNS-server setting, then try nslookup. If DNS fails while basic IP connectivity works, the problem may be related to name resolution rather than the Ethernet link itself.

Data Center Example

A technician may be able to ping a server by IP address but fail to reach it by hostname. That difference is a useful clue: the network path may be working while DNS configuration or records need attention.

Bitcoin Mining Example

A mining machine may be configured with a pool hostname instead of a numeric IP address. DNS must resolve that hostname before the miner can connect to the destination. A DNS failure can therefore look like a pool-connectivity problem even when the local network is otherwise online.

Practice

  1. Explain DNS in one sentence.
  2. Find the DNS-server address configured on your computer.
  3. Run nslookup example.com.
  4. Identify the name you queried and the address returned.
  5. Explain why reaching an IP address but not a hostname can point toward DNS.

Key Takeaway

DNS translates human-friendly names into network information such as IP addresses. For a technician, the essential skills are knowing what DNS does, identifying the configured resolver, testing a lookup, and recognizing when a problem is specifically about name resolution.

15 responses to “OSNTC.006: DNS Basics”

  1. […] technician lesson builds on OSNTC.005: DHCP Basics, OSNTC.006: DNS Basics, and OSNTC.007: MAC Address […]

    Like

  2. […] This connects directly to earlier lessons on default gateways and DNS. […]

    Like

  3. […] earlier DNS Basics lesson is a useful example because DNS can use both UDP and TCP depending on the […]

    Like

  4. […] and NAT solve different problems. The earlier OSNTC.006: DNS Basics lesson covers name resolution. DNS can point a hostname to a public translated address, but the […]

    Like

  5. […] Enter, and a page appears a moment later. Behind that simple action, your computer may perform a DNS lookup, find an IP address, send data through a router, create a transport connection, negotiate […]

    Like

  6. […] sits on top of the same networking stack BitcoinVersus.Tech has already broken down through DNS, TCP, routers, and network interface cards. HTTPS is not a separate Internet—it is a protected […]

    Like

  7. […] often configure time sources using hostnames rather than raw IP addresses. That means a broken DNS path can look like an NTP failure because the client cannot resolve the server […]

    Like

  8. […] names of independently operated seed services. A new node can query those names through the normal DNS system and receive IP addresses of nodes that are likely to be […]

    Like

  9. […] names of independently operated seed services. A new node can query those names through the normal DNS system and receive IP addresses of nodes that are likely to be […]

    Like

  10. […] asks the local resolver to look up seed hostnames, which makes the process dependent on the same DNS concepts used by browsers, servers, and other […]

    Like

  11. […] different caches, different resolvers, or simply different remaining TTLs. The site’s newer DNS Basics lesson provides the beginner model; this cache behavior is what that model looks like during real […]

    Like

  12. […] OSNTC.006: DNS Basics introduced the Domain Name System and the purpose of name resolution. The previous networking lesson, OSNTC.025: DHCP Troubleshooting, moved the technician track from basic service operation into fault isolation. DNS troubleshooting is the natural next step because a host can have a perfectly valid IP address and still appear “offline” to users if names do not resolve. […]

    Like

  13. […] DNS Basics lesson explains the ordinary name-resolution path. DNSSEC adds cryptographic validation to that process. […]

    Like

  14. […] Anycast can spread traffic geographically, a CDN can add distributed capacity, and resilient DNS prevents one overloaded service from becoming a wider […]

    Like

Leave a Reply