Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Doggo – A powerful, human-friendly DNS client for the command line

doggo.mrkaran.dev

Post reply on HN
Print view View original

91–100 of 138 posts

Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line

#91

Post by emmanueloga_ »

mr-karan wrote: post #84
emmanueloga_ wrote: post #67

Is this related to Dog [1]? They look almost identical in functionality. Both ask for the specific query to run (A, AAAA, etc.). Why not default to query all records? (at least when querying a single domain). -- 1: https://github.com/mr-karan/doggo

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...

Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line

#92

Post by [deleted] »

achillean wrote: post #46

We developed "geodns" for situations where you want to do DNS lookups from different regions around the world. For example, ycombinator.com returns different IPs depending on your location: $ geodns ycombinator.com 108.156.133.117 Singapore 108.156.133.21 Singapore 108.156.133.25 Singapore 108.156.133.59 Singapore 108.156.39.26 London 108.156.39.61 London 108.156.39.62 London 108.156.39.64 London 13.32.27.123 Frankfu…

[deleted]

Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line

#97

Post by mr-karan »

varenc wrote: post #77
mr-karan wrote: post #55

Earlier quoted context omitted.

Would this be something close to what you're looking for? alias doggo-all='doggo $1 A AAAA AFSDB APL CAA CDNSKEY CDS CERT CNAME CSYNC DHCID DLV DNAME DNSKEY DS EUI48 EUI64 HINFO HIP HTTPS IPSECKEY KEY KX LOC MX NAPTR NS NSEC NSEC3 NSEC3PARAM OPENPGPKEY RRSIG RP SIG SMIMEA SOA SRV SSHFP SVCB TLSA TSIG TXT URI ZONEMD ${2:+@$2}' doggo-all example.com @1.1.1.1

When I run that: $ doggo google.com A AAAA AFSDB APL CAA CDNSKEY CDS CERT CNAME CSYNC DHCID DLV DNAME DNSKEY DS EUI48 EUI64 HINFO HIP HTTPS IPSECKEY KEY KX LOC MX NAPTR NS NSEC NSEC3 NSEC3PARAM OPENPGPKEY RRSIG RP SIG SMIMEA SOA SRV SSHFP SVCB TLSA TSIG TXT URI ZONEMD It takes 5+ seconds to get a response. Classic `dig` though takes 50ms.

I just pushed the concurrent version of lookups in each resolver. Speed up is quite good around 70-80% on most domains. Will test this more before releasing to main!

https://github.com/mr-karan/doggo/pull/128#issuecomment-2202...

Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line

#99

Post by steph-123 »

An awesome project, I learned about it last year through developing the x-cmd pkg, at that time the latest version was 0.5.7, now it's 1.0.2, it seems necessary to upgrade the version.

Here is a demo video, you can take a look： https://x-cmd.com/pkg/doggo

Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line

#100

Post by mrngm »

kadoban wrote: post #60
robomc wrote: post #47

I have a silly question I guess... why does it print everything out twice? ~ doggo google.com NAME TYPE CLASS TTL ADDRESS NAMESERVER google.com. A IN 296s 142.250.67.14 127.0.2.2:53 google.com. A IN 296s 142.250.67.14 127.0.2.3:53 ~ doggo news.ycombinator.com NAME TYPE CLASS TTL ADDRESS NAMESERVER news.ycombinator.com. A IN 1s 209.216.230.207 127.0.2.2:53 news.ycombinator.com. A IN 1s 209.216.230.207 127.0.2.3:53

Looks like once per nameserver that you're configured to use. I guess just in case they give different answers, which is uncommon in practice.

Try a few queries to an anycasted resolver for the same record. It's rather common that, for example, TTL values differ per response. (the magic trick here is that it's not guaranteed that your requests end up on the same resolver).

You could have a look at https://dnsdiag.org/ that provides a few tools for further introspection in the many (different) answers resolvers can give.

Post reply on HN