[01:08] <cmaloney> I'm still running Ubuntu 18.04. :)
[01:08] <cmaloney> The last of a dying breed
[20:18] <jrwren> i do FIPS things at work. Ubuntu Pro makes that easy. Dealing with 1 distro keeps me on ubuntu.
[20:18] <jrwren> I’m trying to think of ways to resolve a name to an IP from cmdline in a restricted env. I would appreciate any ideas you have:
[20:18] <jrwren> host cmd - not installed in env and pkg not available
[20:18] <jrwren> dig cmd - same as host cmd
[20:18] <jrwren> ping - same as host cmd
[20:18] <jrwren> nslookup - same as host cmd
[20:18] <jrwren> getent hosts - not exactly resolv only, but I used it anyway
[20:18] <jrwren> call perl which is probably installed
[20:18] <jrwren> call python  - same as host cmd
[20:18] <jrwren> busybox?
[20:19] <jrwren> other?
[20:21] <cmaloney> Telnet to port 53? :)
[20:43] <jrwren> it is difficult to write a DNS query and even more difficult to parse the response, else that would have been something I considered.
[20:47] <cmaloney> I know. I'm being slightly cheeky here
[20:48] <cmaloney> I mean, any language that has networking libraries will have something similar for doing DNS lookups
[20:48] <cmaloney> C, C++, etc.
[20:48] <cmaloney> Rust,
[20:48] <cmaloney> the 15,000 libraries that would make up a NodeJS DNS call
[20:48] <cmaloney> like some perverse fire-brigade
[20:49] <jrwren> sure, but what is easiest? do the simplest thing that works.
[21:20] <ben> busybox has nslookup in it
[21:20] <ben> what do you have access to?
[21:55] <jrwren> It is a fips ubuntu20 container where a lot of packages aren't available. e.g. I tried to  install bind-utils or something to get host or dig, but they weren't there, hence the question.