<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Drill on Lead DevOps</title><link>https://lead-devops.blackdevhub.online/en/tags/drill/</link><description>Recent content in Drill on Lead DevOps</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 07 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://lead-devops.blackdevhub.online/en/tags/drill/index.xml" rel="self" type="application/rss+xml"/><item><title>nslookup and drill: DNS resolution in terminal</title><link>https://lead-devops.blackdevhub.online/en/posts/nslookup-drill-dns-resolution/</link><pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate><guid>https://lead-devops.blackdevhub.online/en/posts/nslookup-drill-dns-resolution/</guid><description>&lt;p&gt;The server won&amp;rsquo;t resolve a domain, but pings fly through. No familiar dig at hand — the BIOS is already loading a minimal busybox. Or on a host without bind-tools. nslookup and drill fill this gap: the first one is built into almost everything, the second gives more context when debugging.&lt;/p&gt;&#10;&lt;h2 id="nslookup-interactive-and-one-liner-modes"&gt;nslookup: interactive and one-liner modes&#10;&lt;/h2&gt;&#10;&lt;p&gt;nslookup ships with bind-utils and isc-dhcp-client. It works in two modes.&lt;/p&gt;</description></item></channel></rss>