121–130 of 138 posts
Earlier quoted context omitted.
What does "all records" mean though? `dig` defaults to just show A records and I've kept the behaviour same. Do you mean all possible record types under the sun, or just a bunch of common ones? `MX, AAAA, A, CNAME, TXT` etc ?
I did not realize the list of record types was so long! [1] But I was thinking the common ones, yes. --- 1: https://en.wikipedia.org/wiki/List_of_DNS_record_types#/medi...
Earlier quoted context omitted.
dotnet publish -o . -p:PublishAot=true :) To be fair, I do not think the author understands what static binaries are and why they may or may not want them, and how what Go does differs to what C/C++ toolchain does. I’d be very surprised if they do, being a Go developer. Next time they will learn another excuse to promote their language.
Also to be fair, they did say "by default", and those options you provided must be set because they are not default.
Earlier quoted context omitted.
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.
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.
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.
I'd not encourage the usage of an AUR helper. Just pointing to the AUR page should be enough.
Earlier quoted context omitted.
What does "all records" mean though? `dig` defaults to just show A records and I've kept the behaviour same. Do you mean all possible record types under the sun, or just a bunch of common ones? `MX, AAAA, A, CNAME, TXT` etc ?
I did not realize the list of record types was so long! [1] But I was thinking the common ones, yes. --- 1: https://en.wikipedia.org/wiki/List_of_DNS_record_types#/medi...
Earlier quoted context omitted.
You can't really query all DNS records these days anymore by using the ANY query type. The closest alternative is to run dig across all record types. At Andrew McWatters & Co., we use a small internal utility called digany(1)[1][2] that does this for you. [1]: https://github.com/andrewmcwattersandco/digany [2]: https://github.com/andrewmcwattersandco/digany/blob/main/dig... andrewmcwatters@Andrews-MacBook-Pro digany…
or AXFR... but it is allowed on even less places than ANY.
Very nice to also have it dockerized. You might just want to add in the documentation the `--rm` parameter for cleanup after running and `-t` for the colors. So it will be docker run --rm -it ghcr.io/mr-karan/doggo:latest mrkaran.dev MX
Just curious, but why go through all the trouble to create a docker container for a DNS cli utility with no dependencies?
The q client has a feature comparison: https://github.com/natesales/q?tab=readme-ov-file#feature-co...