Skip to content

Appendix G — Glossary

A record — Maps a name to an IPv4 address: “this name lives at this street address.” Ch 10.

AAAA record — The IPv6 equivalent of an A record, mapping a name to an IPv6 address. Ch 10.

ACL — Access control list: an ordered set of allow or deny rules, as in a firewall or tailnet policy. The guard’s clipboard. Ch 14.

ACME — The protocol that lets a server prove domain control and receive a certificate automatically. Caddy speaks it by default. Ch 9.

Agent forwarding — Lets a remote server use your local SSH keys through your connection. Handy, and risky on any machine you do not fully trust. Ch 6.

ALIAS (ANAME) — A provider-specific record that acts like a CNAME at the apex, flattened to A records by the DNS host. It is not standard DNS. Ch 11.

Anycast — One IP announced from many places, so each visitor reaches the nearest one. It is how large CDNs spread load. Ch 17.

Apex — The bare domain, like pipeslab.in, with no subdomain. A CNAME cannot sit here, which is why ALIAS exists. Ch 11.

ASN — Autonomous System Number: the ID of one network in BGP, such as an ISP or a cloud provider. The district number on the map. Book 1.

Authoritative server — The DNS server holding the official answers for a zone. Your DNS host’s nameservers are authoritative for your domain. Ch 10.

authorized_keys — The file listing the public keys allowed to log in as a user, usually ~/.ssh/authorized_keys. The guest list at the door. Ch 6.

Backup (3-2-1) — Three copies of your data, on two kinds of media, with one copy off-site. A backup you have never restored is a hope. Ch 19.

Bastion (jump host) — A hardened machine you pass through to reach private machines behind it. A tailnet or tunnel often replaces it now. Ch 16.

BGP — Border Gateway Protocol: how networks announce which address ranges they can reach. The road-map argument between districts. Book 1.

Bind address — The local IP a program listens on. 0.0.0.0 means every interface; 127.0.0.1 means this machine only. Ch 3.

CA (certificate authority) — The trusted signer that vouches a certificate belongs to a name. Ch 9.

CAA record — DNS record naming the only CAs allowed to issue certificates for your domain. Ch 10.

Caddy — A reverse proxy that gets and renews HTTPS certificates by itself. The receptionist with the paperwork covered. Ch 8.

CGNAT — Carrier-grade NAT: your ISP shares one public address among many homes. A gated society inside a township. Ch 1.

Chain of trust — The signed links from your certificate up to a root CA your browser already trusts. Ch 9.

CIDR — Notation like 10.0.0.0/24 for a block of addresses. A whole street range on one sign. Ch 1.

Cloudflare Tunnel — An outbound link from your server to Cloudflare, so no inbound door faces the street. Ch 17.

CNAME record — Makes one name an alias for another. It cannot sit at the apex. Ch 10.

Container — A process with its own filesystem view and limits, sharing the host kernel. A sealed office, not a building. Ch 7.

Control plane — The part that decides routes, rules and certificates. The city council, not the traffic. Ch 18.

Cookie Domain attribute — Which hostnames a browser sends a cookie to. Set it too broadly and sibling subdomains share your session. Book 1.

CT logs — Public, append-only logs of every certificate issued. Anyone can check what was issued for their names. Ch 9.

Daemon — A background program with no terminal, started at boot. The night watchman of the server. Ch 5.

Data plane — The part that moves packets and requests, following rules set by the control plane. Ch 18.

DDoS — A flood of traffic meant to exhaust your capacity. Weather, not personal. Ch 17.

Default deny — Block everything unless a rule allows it. The guard’s default answer is no. Ch 14.

DERP — Tailscale’s relay servers, used when a direct path cannot be punched through. Ch 16.

DHCP — Hands a device its address, gateway and DNS server when it joins a network. Ch 1.

DKIM — A signature on outgoing mail, checked against a key in DNS. A tamper-proof seal. Ch 13.

DMARC — Tells receivers what to do when SPF or DKIM fail, and where to send reports. Ch 13.

DNS — The system that turns names into addresses and other records. The city directory. Ch 10.

DNS-01 — An ACME challenge proven by a TXT record in DNS. The one that unlocks wildcards. Ch 9.

DNSSEC — Signs DNS answers so resolvers can detect forgeries. More trust, more moving parts. Ch 10.

Docker — Builds and runs containers from images under a daemon. Useful, and it can open doors past your firewall. Ch 7.

DOCKER-USER chain — The iptables chain Docker consults first, where your container firewall rules belong. Ch 14.

DoH / DoT — DNS over HTTPS and DNS over TLS: queries wrapped in encryption. Ch 10.

Drop vs reject — Drop discards silently; reject sends back a refusal. Drop makes scanners wait. Ch 14.

Dynamic port forwarding — SSH opens a local SOCKS proxy that sends your traffic out through the server. Ch 6.

Egress — Traffic leaving your server or network. Outbound rules are the ones people forget. Ch 14.

Ephemeral port — A temporary high port the OS picks for the client side of a connection. Ch 2.

eTLD+1 — The registrable domain, like pipeslab.in: one label past the public suffix. Ch 11.

Exit node — A tailnet device that carries your internet traffic on your behalf. Ch 16.

Fail2ban — Watches logs for repeated failed logins and bans the address for a while. Ch 14.

Firewall — Rules deciding which packets may pass. The guard with a clipboard. Ch 14.

Forward proxy — Acts for clients going out, like a corporate web filter. The reverse of a reverse proxy. Ch 8.

gTLD (generic top-level domain) — A broad ending like .com, .org or .app, run under contracts with ICANN. The big avenues of the city. Ch 11.

ccTLD (country-code top-level domain) — A two-letter ending tied to a country, like .in or .uk. Local lanes with local rules. Ch 11.

HSTS — HTTP Strict Transport Security: a response header telling browsers to use HTTPS for your domain for a stated period. A standing order at reception: never offer the plain door. Ch 9.

HTTP-01 — An ACME challenge where the CA fetches a file from your server on port 80 to prove you control the name. Simple, but the name must point at you and port 80 must be open. Ch 9.

Hypervisor — Software that carves one physical machine into virtual machines, each with its own kernel. A building split into flats. Ch 4.

ICANN — The nonprofit that coordinates the global naming system, including the root zone and the rules for top-level domains. It writes the city’s rulebook rather than running every street. Ch 11.

ICMP — The control messages of IP, such as “destination unreachable” and echo, which is ping. Blocking all of it by reflex breaks path discovery. Ch 2.

Ingress — Traffic arriving at your server or network from outside. Its opposite is egress. Ch 14.

iptables / nftables — Linux tools for writing packet filtering rules. iptables is the older one; nftables is its newer replacement. Both are the guard’s clipboard, living in the kernel. Ch 14.

IPv4 — The 32-bit address format, like 203.0.113.10. It is scarce enough that networks lean on NAT and CGNAT to stretch it. The original street numbering. Ch 1.

IPv6 — The 128-bit address format with far more room, written in hex groups like 2001:db8::1. Wider streets, same idea. Ch 1.

journalctl — The command that reads the systemd journal, the log store on modern Linux. Your first stop when a service misbehaves. Ch 5.

known_hosts — The file where your SSH client remembers each server’s host key. When that key changes, SSH warns you, because someone may be standing at the gate. Ch 6.

KVM — Kernel-based Virtual Machine, the hypervisor built into Linux. It turns the kernel itself into a flat-maker. Ch 4.

Latency — The time a packet takes to make the trip. Distance and hops set its floor. Bandwidth is a different thing: a wide road can still have a long walk. Ch 2.

Let’s Encrypt — A free, automated CA that issues certificates over ACME. Caddy uses it by default. Ch 9.

Listening socket — A socket a program has opened to wait for incoming connections on an address and port. It is a numbered door with someone behind it, waiting. Ch 3.

Load balancer — Spreads incoming requests across several backends. The receptionist with a row of desks. Ch 18.

Local forward — An SSH tunnel that makes a port on your laptop lead to a port on the far side. Set with the -L flag. Ch 6.

localhost — The name for this machine itself, at address 127.0.0.1 (and ::1 for IPv6). A service bound only here is visible to nobody else. “Works on localhost” is cursed for a reason. Ch 3.

MagicDNS — Tailscale’s naming feature, giving each device in your tailnet a short name that resolves privately. The tailnet’s own directory. Ch 16.

MITM (man in the middle) — An attacker sitting on the path, relaying or altering traffic. Unlike the doorknob-rattlers, this is targeted, and TLS exists largely to make it fail. Ch 9.

MTU — Maximum transmission unit: the largest packet a link carries without splitting. Set it wrong and some large requests vanish quietly. Ch 2.

MX record — DNS record naming the servers that accept mail for a domain, with priorities. The mail room’s entry in the directory. Ch 13.

NAT — Network address translation: a router rewrites addresses so many devices share one public IP, and replies find their way back. The gated society’s gate guard. Ch 1.

NAT traversal (hole punching) — Techniques that let two devices behind NAT connect directly, each sending outward first so the gates recognise the reply. Ch 16.

Negative caching — Resolvers remember “this name does not exist” for a period set in the zone’s SOA record. A new name can look missing for a while after you create it. Ch 10.

nginx — A widely used web server and reverse proxy, configured in plain text files. Like Caddy, it is a receptionist. Ch 8.

NS record — Names the authoritative nameservers for a zone. Set at your registrar, it tells the world where the directory lives. Ch 10.

NSG / security group / security list — Cloud firewall rule sets at the provider level, before packets reach your server. Names vary: AWS uses security groups, and Oracle Cloud has both security lists and NSGs. Ch 14.

OOM killer — The Linux kernel’s last resort when memory runs out: it picks a process and kills it, and your app can vanish with no error in its own logs. Check journalctl -k to see the kill. Ch 19.

Orange cloud — Cloudflare’s dashboard shorthand for a DNS record that is proxied through Cloudflare, so visitors hit the doorman and not your street address. The grey cloud means DNS only. Ch 17.

Origin — The real server behind a proxy or CDN, the office at the back that only the receptionist should be able to reach. Locking the origin to Cloudflare or a Tunnel stops people walking around the doorman. Ch 17.

PaaS — Platform as a service, where a provider runs the machines, the OS and often the deploys for you, like a serviced office with the building manager included. You trade control for less 2 a.m. maintenance. Ch 4.

Packet — A small chunk of data with a header that says where it is going, the unit that every network hop forwards. Think of an envelope with a street address on it, passed from post office to post office. Ch 2.

Passphrase — The password that unlocks an SSH private key on your laptop. It protects the key file itself, so a stolen copy is not instantly usable. Ch 6.

Port — A number from 0 to 65535 that tells the server which app should receive a packet, the numbered door of the office. Ports are not physical, but they behave like doors in the mental model. Ch 3.

Port scan — A sweep that knocks on many ports to see which ones answer, the doorknob-rattler’s favourite trick. Scans are weather, not personal, and your guard should expect them. Ch 15.

Private IP — An address reserved for internal networks, such as 10.x, 172.16 to 172.31, and 192.168.x, that the public internet does not route. Your lab’s 10.0.0.5 is one, an internal street that only neighbours can reach. Ch 1.

PTR record — A DNS record that maps an IP address back to a name, the reverse of an A record. Mail servers check it, and a missing one makes your mail look suspicious. Ch 10.

Public IP — An address routable on the open internet, the street address the rest of the city can use. Your home router may have one, and your VPS normally does. Ch 1.

Public Suffix List — A community-maintained list of suffixes like co.uk and github.io where people register names, so browsers know where one site ends and another begins. It is the reason cookies do not leak across unrelated sites on a shared suffix. Ch 11.

QUIC — A transport protocol built on UDP that bundles encryption and the handshake into one trip, and powers HTTP/3. It keeps working when your phone switches from Wi-Fi to mobile data. Ch 9.

RDAP / WHOIS — The lookup services that tell you who registered a domain and when it expires. WHOIS is the old text protocol, and RDAP is its structured, JSON-speaking successor. Ch 11.

Recursive resolver — The DNS server that does the legwork for your laptop, asking the root, then the TLD, then the authoritative server, and caching the answers. It is the clerk at the city directory counter, and your ISP or 1.1.1.1 often plays this role. Ch 10.

Redemption period — The grace window after a domain expires, when the registrar can still renew it for a fee before it is deleted. Missing renewal here is how a lapsed domain ends up in a stranger’s hands. Ch 11.

Registrar — The company you buy a domain name from, the estate agent who records the sale. It sends your details to the registry and handles renewals. Ch 11.

Registry — The operator of a top-level domain, such as the one running .com or .in, the civic office that keeps the master list. Registrars sell names, but the registry holds the records. Ch 11.

Remote forward — An SSH tunnel that opens a port on the remote server and sends traffic back to your laptop, so the server can reach a service you run locally. It is the corridor you dig in the other direction. Ch 6.

Reverse DNS — The lookup from an IP address to a name, using PTR records under in-addr.arpa. It is handy for logs and mail reputation, and not a required part of the city directory. Ch 10.

Reverse proxy — A server that stands at the front of your apps, takes requests from the street, and passes them to the right app, the receptionist who knows which office to call. Caddy and nginx both play this role. Ch 8.

RPO / RTO — Recovery point objective is how much data you can afford to lose, measured as time since the last backup. Recovery time objective is how long you can afford to be down. Write both down before your next outage, not during it. Ch 19.

RST — A TCP reset, a packet that says the connection is over and should be torn down now. You see it when a port is closed or a stateful firewall rejects a connection, the receptionist slamming the door. Ch 2.

SFTP — File transfer over an SSH connection, so the same keys and the same encryption protect your uploads. It is not the old FTP protocol with a letter added, despite the name. Ch 6.

SNI — Server Name Indication, the hostname sent in plain text at the start of a TLS handshake so one IP can serve many sites. It is the name on the envelope that tells the receptionist which office to open. Ch 9.

SOA record — The start-of-authority record at the top of a zone, which names the primary server, the contact, the serial number and the timers. Secondary servers read it to know when to refresh. Ch 10.

Socket — The operating system’s handle for one end of a network conversation, usually an IP address plus a port on each side. A listening socket is the door that is open and waiting for knocks. Ch 3.

SPF — A DNS TXT record that lists which servers may send mail for your domain, the guest list at the front desk. Receivers check it, and it works best alongside DKIM and DMARC. Ch 13.

Split-horizon DNS — Serving different answers for the same name depending on who asks, such as a private address inside your network and a public one outside. It is the directory with two editions, one for insiders. Ch 10.

SRV record — A DNS record that says which host and port offer a given service, so clients can find it without a hardcoded port. It is a signpost that says the service lives at this door on that building. Ch 10.

SSH — Secure Shell, the encrypted protocol you use to log in to a server and move files. It uses keys, not passwords, in the setup this book recommends. Ch 6.

sshd — The SSH server daemon that listens on port 22 and checks who is knocking. Its config lives in /etc/ssh/sshd_config, and you should change it with a second session open. Ch 6.

Stateful firewall — A firewall that remembers open connections, so replies to your outgoing requests are allowed back in while unsolicited inbound packets are dropped. The guard keeps a clipboard of who went out. Ch 14.

Subdomain — A name placed in front of a domain, such as app.pipeslab.in, that you can point at a different server. It is a department with its own door inside the same building. Ch 12.

Subdomain takeover — An attack where a DNS record points to a service you no longer use, and an attacker claims that service and serves content from your name. Clean up dangling CNAMEs when you retire an app. Ch 12.

Subnet — A slice of IP addresses that share a common prefix, written like 10.0.0.0/24. It is a block of streets in the same neighbourhood, and devices on it can usually talk to each other directly. Ch 1.

Sudo — The command that runs one action with root privileges after you prove who you are, so daily work does not happen as root. It is the escort you call only when the job needs one. Ch 5.

SYN scan — A port scan that sends only the first half of a TCP handshake and reads the reply, so it is quick and quiet. The doorknob-rattler’s fast pass down the row. Ch 15.

systemd — The init system on most modern Linux servers, which starts services at boot, restarts them when they crash, and keeps their logs. Your Node app should run as a unit, not inside a terminal tab. Ch 5.

Tailnet — The private network Tailscale builds across your devices, with each machine getting a stable 100.x address. Think of it as a gated township that only your buildings belong to. Ch 16.

Tailscale — A service that sets up WireGuard tunnels between your devices for you, handling keys and NAT traversal. It is the private corridor system that connects your buildings without a public door. Ch 16.

TCP — The reliable transport protocol that numbers every packet, retransmits losses and delivers bytes in order. Web pages, SSH and most databases ride on it. Ch 2.

Three-way handshake — The SYN, SYN-ACK, ACK exchange that opens a TCP connection before any data flows. It is the two parties confirming they can both hear each other before they start talking. Ch 2.

Timeout — A limit on how long a connection or request waits before giving up. A timeout on a closed port looks different from a refused one, and that difference is useful when you debug. Ch 14.

TLD — A top-level domain, the last label in a name, such as com, in or dev. The registry for each TLD runs its own part of the city directory. Ch 11.

TLS — Transport Layer Security, the protocol that encrypts a connection and proves the server is who it claims to be, using certificates. HTTPS is HTTP wrapped in TLS. Ch 9.

tmux — A terminal multiplexer that keeps your shell running on the server even when your laptop sleeps or your SSH session drops. It is a workshop bench that survives you walking out the door. Ch 6.

TTL — Time to live, a number in a DNS record that says how long resolvers may cache the answer, in seconds. Lower it before a migration so the change spreads fast, then raise it again afterwards. Ch 10.

UDP — A lightweight transport protocol with no handshake, no retransmission and no ordering guarantees. It is a postcard: fast, cheap, and you find out later if it got lost. DNS and QUIC both use it. Ch 2.

UFW — Uncomplicated Firewall, a front end for iptables on Ubuntu that writes simple allow and deny rules. It is a clipboard template for the guard, and it still needs default deny to be useful. Ch 14.

VCN / VPC — Virtual cloud network (Oracle) or virtual private cloud (AWS and others), the private address space your cloud servers share. It is the gated township your VPS lives in, with its own street plan. Ch 4.

VPN — A virtual private network, which encrypts traffic between you and a remote network so it looks like you are inside it. Tailscale and WireGuard are modern VPNs that suit a small team. Ch 16.

VPS — A virtual private server, a slice of a physical machine that behaves like a full server with its own OS and public IP. Your lab box at 203.0.113.10 is one. Ch 4.

WAF — A web application firewall that inspects HTTP requests for attacks such as SQL injection or bad bots. It is a guard who reads the visitor’s letter, not just their address. Ch 17.

WebSocket — A long-lived connection that starts as an HTTP request and then keeps both sides talking, useful for chat and live dashboards. Your reverse proxy needs to pass the upgrade through. Ch 8.

Wildcard — A certificate or DNS record that covers every name at one level, written as *.pipeslab.in. It saves you from issuing one certificate per subdomain, but it covers only one label deep. Ch 12.

WireGuard — A small, modern VPN protocol built into the Linux kernel, with keys and a simple config. Tailscale uses it under the hood, and it is the private tunnel between your buildings. Ch 16.

Zero trust — A security model that checks every request on identity and device, not on whether it came from inside the network. The guard checks the badge at every door, not just the gate. Ch 17.

Zone — The part of the DNS tree that one set of records is responsible for, usually one domain and its records. It is the directory section one clerk maintains. Ch 10.

Book 2 of a series. Book 1: The Glue.