nslookup is a BIND DNS lookup CLI — pick a name, print Server and Address. It is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
Accidental sysadmins land on nslookup because nslookup example.com shows Name and Address without a dashboard. Then disk is at 91%, nginx dies, and last night's Server line does not say what to run. A filling /var is a Tink warning; it is not a BIND query.
Tink is the other job: detect the issue on the machine, say why it happened in plain English, propose the command, and run it only after you approve. Keep using nslookup if you already want a lookup against a resolver. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | nslookup |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Install bind-utils / dnsutils, then run nslookup against a name every time DNS looks wrong |
| What you get | Working monitoring, diagnosis, and approved fixes | A one-shot lookup: Server, Address, Name, Address — only while you are watching |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Open source. You still pay the person who SSHs in after the outage |
| Hidden costs | None — fully managed | Which server, interactive vs one-shot, TCP vs UDP, and whether anyone was watching when NXDOMAIN hit |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Active DNS query. nslookup does not parse auth.log or propose a command |
| Configuration | None after install — heuristics and AI | Name, type, server, set debug, and whether /etc/resolv.conf is even the resolver the app uses |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | No — you read Server/Address yourself |
| Fix execution | Proposes and executes approved commands with an audit trail | Monitoring only — nslookup cannot restart nginx, free disk, or rotate a cert |
| Alerting | Built-in across 8 channels | None by default — nslookup is a snapshot; paging is extra |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Live lookup only — nslookup does not forecast fill time or a quiet disk going bad later |
| SSH brute-force detection | Built-in — parses auth.log every scan | Not included — nslookup does not read host auth.log or journald |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | If the host is down you cannot SSH into nslookup either |
| Public status page | Shareable URL with 90-day history | Not included — nslookup has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | Not included — a Name/Address pair is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire something else into PagerDuty |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | SSH + nslookup. No mechanic you text when /var filled |
| Learning curve | None — works after install | Low to launch; higher to map SERVFAIL to the disk that filled |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Operators who already want a BIND dump and will still SSH in when the box is sick |
Keep using nslookup when you already want that exact job:
The lookup is cheap to install. A working ops loop for five Linux boxes is not:
For a 5-server team, Tink Mechanic at $45/month is cheaper than the engineer who opens nslookup after the outage, and every scan includes a diagnosis a quiet BIND lookup will not type.
No SSH homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs ping · Tink vs mtr · Tink vs iperf3