LOGRESOLVE(1)

πŸ“¦
version 2.4.69 Β· 3 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, debian bookworm, debian trixie, fedora 43, fedora 44, nixpkgs unstable, ubuntu stonking

✨ LOGRESOLVE πŸ’…

okay so bestie, welcome to logresolve β€” the little Apache HTTP Server tool that takes your access log's IP addresses and turns them into hostnames. it's giving ✨ DNS glow-up ✨


🌸 SYNOPSIS 🌸

logresolve [ -s filename ] [ -c ] < access_log > access_log.new

πŸ¦‹ SUMMARY πŸ¦‹

logresolve is a post-processing program β€” like, it doesn't run live, it goes after the fact β€” and its whole job is resolving the IP-addresses inside Apache's access logfiles. 🫢

and the way it protects your nameserver from getting absolutely bodied by a million lookups? it has its very own internal hash-table cache. no cap. that means each IP number gets looked up only the first time it shows up in the log file. after that, it's remembered. queen behavior. πŸ‘‘

it takes an Apache log file on standard input. and heads up, this part matters:

  • the IP addresses must be the first thing on each line
  • and they must be separated from the rest of the line by a space

that's it, that's the whole contract. no space, no service. 😭


πŸŽ€ OPTIONS πŸŽ€

  • -s filename β€” specifies a filename to record statistics. so if you wanna know what went down during the resolve, this is where you send the receipts. πŸ“
  • -c β€” this causes logresolve to apply some DNS checks. like, after finding the hostname from the IP address, it looks up the IP addresses for that hostname and checks that one of these matches the original address. it's the double-check, the vibe check, the "wait, are you sure that's you?" 🧚✨

lowkey important: that -c check is an extra round of lookups, so it's doing more work on purpose. it's not a bug, it's a feature, bestie. πŸ’–

and that's the whole page, periodt. this one came from the Apache HTTP Server, dated 2026-04-30. mwah, go resolve some hostnames. πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from