3 ms·

TIL there's also dog[1] Which is probably also common typo for "dig" [1] https://github.com/ogham/dog https://github.com/ogham/dog

by ck45 2y ago

hk__2 2y ago
doggo is actually dog written in Go.
linsomniac 2y ago
I went to switch over to "dog" last week but it looks abandoned. I couldn't get a download to work because of outdated dependencies, and IIRC I couldn't get it to build, so I just gave up on it after seeing the latest release is 4 years old.
- renewiltord 2y ago
  Upgrade the openssl dependencies if you are on new Ubuntu: ubuntu $ (new) target/release/dog google.com A google.com. 2m13s 142.250.189.206 NS 15h15m07s A "i.root-servers.net." NS 15h15m07s A "d.root-servers.net." NS 15h15m07s A "a.root-servers.net." NS 15h15m07s A "b.root-servers.net." NS 15h15m07s A "c.root-servers.net." NS 15h15m07s A "f.root-servers.net." NS 15h15m07s A "e.root-servers.net." NS 15h15m07s A "h.root-servers.net." NS 15h15m07s A "m.root-servers.net." NS 15h15m07s A "j.root-servers.net." NS 15h15m07s A "k.root-servers.net." NS 15h15m07s A "g.root-servers.net." NS 15h15m07s A "l.root-servers.net." A a.root-servers.net. 2d10h37m14s + 198.41.0.4 ubuntu $ (new) git status On branch master Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: Cargo.lock modified: dns-transport/Cargo.toml no changes added to commit (use "git add" and/or "git commit -a") ubuntu $ (new) git diff dns-transport/Cargo.toml diff --git a/dns-transport/Cargo.toml b/dns-transport/Cargo.toml index 67552c3..d68d542 100644 --- a/dns-transport/Cargo.toml +++ b/dns-transport/Cargo.toml @@ -19,6 +19,8 @@ log = "0.4" # tls networking native-tls = { version = "0.2", optional = true } +openssl-sys = ">=0.9.102" +openssl = ">=0.10.64" # http response parsing httparse = { version = "1.3", optional = true }
- Zambyte 2y ago
  That seems crazy to me that a DNS client is broken after only 4 years due to incompatibility dependencies! I was going to suggest that maybe it's just completed software, but wow, this makes me really want to stay away from the Rust ecosystem.
  - gunapologist99 2y ago
    Not sure why you're being downvoted, because this is how the JS and Python ecosystems are becoming as well. Obviously, there's a lot of innovation that's happening (or at least the authors think so), but it's still possible to move a package forward without breakage. It'd be great if communities could adopt the Go backwards compatibility promise[0] (it's best-effort, after all) so that packages continue to compile for a decade into the future and only introduce breaking changes for security reasons. It's actually not that difficult to do -- just needs to be made an important goal of any project, and it makes it much easier to trust the stability of the dependency. 0. https://go.dev/blog/compat https://go.dev/blog/compat

TIL there's also dog[1] Which is probably also common typo for "dig" [1] https://github.com/ogham/dog https://github.com/ogham/dog

by ck45 2y ago

TIL there's also dog[1] Which is probably also common typo for "dig" [1] https://github.com/ogham/dog https://github.com/ogham/dog

hk__2 2y ago

doggo is actually dog written in Go.

linsomniac 2y ago

I went to switch over to "dog" last week but it looks abandoned. I couldn't get a download to work because of outdated dependencies, and IIRC I couldn't get it to build, so I just gave up on it after seeing the latest release is 4 years old.

renewiltord 2y ago
Upgrade the openssl dependencies if you are on new Ubuntu: ubuntu $ (new) target/release/dog google.com A google.com. 2m13s 142.250.189.206 NS 15h15m07s A "i.root-servers.net." NS 15h15m07s A "d.root-servers.net." NS 15h15m07s A "a.root-servers.net." NS 15h15m07s A "b.root-servers.net." NS 15h15m07s A "c.root-servers.net." NS 15h15m07s A "f.root-servers.net." NS 15h15m07s A "e.root-servers.net." NS 15h15m07s A "h.root-servers.net." NS 15h15m07s A "m.root-servers.net." NS 15h15m07s A "j.root-servers.net." NS 15h15m07s A "k.root-servers.net." NS 15h15m07s A "g.root-servers.net." NS 15h15m07s A "l.root-servers.net." A a.root-servers.net. 2d10h37m14s + 198.41.0.4 ubuntu $ (new) git status On branch master Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: Cargo.lock modified: dns-transport/Cargo.toml no changes added to commit (use "git add" and/or "git commit -a") ubuntu $ (new) git diff dns-transport/Cargo.toml diff --git a/dns-transport/Cargo.toml b/dns-transport/Cargo.toml index 67552c3..d68d542 100644 --- a/dns-transport/Cargo.toml +++ b/dns-transport/Cargo.toml @@ -19,6 +19,8 @@ log = "0.4" # tls networking native-tls = { version = "0.2", optional = true } +openssl-sys = ">=0.9.102" +openssl = ">=0.10.64" # http response parsing httparse = { version = "1.3", optional = true }
Zambyte 2y ago
That seems crazy to me that a DNS client is broken after only 4 years due to incompatibility dependencies! I was going to suggest that maybe it's just completed software, but wow, this makes me really want to stay away from the Rust ecosystem.
- gunapologist99 2y ago
  Not sure why you're being downvoted, because this is how the JS and Python ecosystems are becoming as well. Obviously, there's a lot of innovation that's happening (or at least the authors think so), but it's still possible to move a package forward without breakage. It'd be great if communities could adopt the Go backwards compatibility promise[0] (it's best-effort, after all) so that packages continue to compile for a decade into the future and only introduce breaking changes for security reasons. It's actually not that difficult to do -- just needs to be made an important goal of any project, and it makes it much easier to trust the stability of the dependency. 0. https://go.dev/blog/compat https://go.dev/blog/compat