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

61–70 of 138 posts

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

#61

Post by mr-karan »

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

Just tried on my Adguard DNS server, I am only getting one entry. I think it's related to your nameserver configuration. Could you try reproducing with specifying a custom one, with @1.1.1.1 or something?

  doggo google.com --short
  142.250.185.238

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

#62

Post by kevin_nisbet »

metadat wrote: post #58
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…

Is that because it's behind cloudflare? I'm pretty sure it still runs primarily on a single server in a Colo (i.e. except in times of hardware failure or other physical realities).

whois is returning AWS and I don't see any of the normal cloudfront headers, but I do see a server header of nginx. So it doesn't look like cloudflare to me, I'd guess they're just running some ec2 instances with nginx configured to give the exact behaviour they need (as I recall they return cached pages to non logged in users, which is why you can sometimes log out and get the page to load when they're having issues). I also see awsdns in their ns records, so it looks to be like they're just doing Geo-dns in route53 to route to the closest instance they're running.

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

#63

Post by sadops »

throwaway894345 wrote: post #48
TZubiri wrote: post #45

Earlier quoted context omitted.

So like dig but I have to compile build, configure, audit and trust instead of just having it packaged in my OS, nice.

1. You have to audit/trust any software whether or not it’s distributed as part of your OS 2. What is there to configure? 3. It’s a Go program, so compilation happens transparently on installation provided the developers don’t release broken code. This isn’t the C/C++ world where you have complex bespoke build systems that only seem to work on the developers’ machines.

Except package repositories have maintainers, who tend to be trustworthy parties. Compare the number of supply chain attacks Debian's apt repos have compared to, say, npm.

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

#64

Post by sadops »

lynndotpy wrote: post #39
wiseowise wrote: post #31

Is there any reason why so many of those tools are written in Go? Is it because of a stdlib or just accidental?

Go is produces (mostly) statically compiled binaries by default. No runtime, no interpreter, no dependencies. Python, Java, JavaScript, C#, etc. can't say the same.

[flagged]

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

#65

Post by sadops »

kortex wrote: post #23
v101 wrote: post #20

[flagged]

What's stupid about it? Dig was an early and widespread DNS CLI tool. "dog" is a logical name for a next-gen dns cli, and of course that exists. "Doggo" is both a pretty standard linguistic drift pattern of English slang (random -> rando, weird -> weirdo), a common internet term of endearment for "dog", and a logical derivation of *-go for go-based tools and software.

Surprised nobody went for "dug", à la DigDug.

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

#66

Post by hackmiester »

jmduke wrote: post #29

Shameless plug for folks looking for something similar, but on the web: I was fed up with Google's slow/janky dig webface, so built my own. (Still very WIP, but already works better as a daily driver than Google's!) https://www.shovel.report/ycombinator.com

This is pretty cool! But what does it mean when something is listed under "Services"? For example, one of my "services" is "52.45.50.190/32", an AWS IP. What does that actually mean? How did that IP get there?

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

#67

Post by emmanueloga_ »

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

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

#68

Post by fragmede »

lemcoe9 wrote: post #49

Another shameless plug for my website, you can use ipkitten.com to get your public IP address from your terminal: $ curl ipkitten.com 27.44.144.144 And if you visit it in a browser, you get your IP address and a kitten GIF!: https://ipkitten.com

Just don't let grow up and eat http://ipchicken.com.

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

#69

Post by fragmede »

jachee wrote: post #56
nullindividual wrote: post #53

Earlier quoted context omitted.

icanhazip.com is another service which does this.

And the easy-to-remember-for-Unix-nerds: ifconfig.me/ip

if you use curl it'll do user agent detection and just give you your ip

    curl ifconfig.me

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

#70

Post by KingOfCoders »

mr-karan wrote: post #52
arccy wrote: post #42

Earlier quoted context omitted.

I guess not using one of the proxies? for some reason their v1.0.0 commit isn't attached to anything... https://github.com/mr-karan/doggo/commit/fe3958594df46c000ef...

Just pushed a minor patch release. Tagged on main: https://github.com/mr-karan/doggo/commit/8f60428f6ae154918d9...

Installs now but installs as `cmd` not `doggo`
Post reply on HN