linuxlab.io
Tutorials▾
  • Linux & networking
    File system, processes, TCP/IP, BGP and OSPF
    →
  • Terraform & IaC
    HCL, state, plan/apply on a LocalStack sandbox
    →
  • Git & GitHub
    Object model, plumbing, branching, GitHub Actions
    →
All tutorials →
PricingAboutSign inCreate account
/
  • Введение
  • Уроки
  • How it works
  • Симулятор
  • База знаний
  • Собеседование
Lessons
Footer
linuxlab-TutorialsPricingAboutPrivacy & cookies
Copyright © 2026 LinuxLab. All rights reserved.

← из прошлого урока

L3 connectivity is in place; the machines can see each other by IP. But people do not remember IPs, they remember names. Next comes DNS: resolvers, /etc/resolv.conf, and how dig shows the real path of a query.

← к прошлому уроку

Средний

DNS: how a name becomes an address

12 мин · урок входит в курс «Средний»

When you write ping example.com, the kernel cannot work with names; it needs an IP address. The name has to be resolved, which is dns-resolution. That work is handled by a combination of /etc/hosts (a static local file), /etc/resolv.conf (the address of the DNS server for everything that is not in hosts), and the NSS library (it decides in what order to query them).

This sandbox has no internet, so real DNS queries going out will not go through, but you can bring up local names through /etc/hosts and try the getent, dig, and host tools.

Урок закрыт

Чтобы запустить sandbox и пройти этот урок целиком, нужен соответствующий курс. Внутри - ещё много практических уроков того же уровня и сквозной прогресс.

Купить курсВойти← Все уроки

дальше →

Names resolve to addresses, and everything connects. Now the reverse task: stop everything from connecting. Next comes nftables: tables, chains, dropping by port, and how the pcap shows a packet killed before it arrived.

Открыть превью: Firewalling with nftables: allow, deny, inspectв курсе «Средний» - /pricing
Footer
linuxlab-
Copyright © 2026 LinuxLab. All rights reserved.
Tutorials
Pricing
About
Privacy & cookies