I’m still waiting for somebody to write a little CLI that does all these tests and prints out a report. Imagine how many thousands of hours it would save if that tool came installed by default on all systems.
$ is_it_up https://jvns.ca
ping: 80ms
DNS: resolving 1.2.3.4
system DNS: resolving 1.2.3.4
TLS: certificate valid for 23 more days
HTTPS: got 200 OK
All good!
what do you mean by this? I’m curious because i hear “it’s always DNS” a lot and that’s not my experience at all – I’ve found that some networking issues are caused by DNS and some aren’t.
It does feel like weird/inexplicable issues are disproportionately likely to be caused by DNS though, because non-DNS problems are more straightforward to diagnose.
A lot of DNS debugging is done with dig, but as dig is made with the same libraries as BIND8/9 (the most used DNS server out there), what are you actually debugging/testing? drill has nothing in common with either NSD nor BIND. During the development process we are actually uncovering obscure bugs in NSD and BIND (and in drill itself).
…but as we are not talking about testing DNS implementations, that does not seem too relevant? What other advantages does drill have compared to dig?
I’m still waiting for somebody to write a little CLI that does all these tests and prints out a report. Imagine how many thousands of hours it would save if that tool came installed by default on all systems.
Bonus when an error happens, it prints out the command to replicate that exact test.
Welp this should be fun to write.
yes please! I’m to lazy and sidetracked with other things at the moment.
It’s not DNS -> it’s never DNS -> it can’t be DNS -> it’s DNS
Huh, in my experience it’s almost always DNS.
what do you mean by this? I’m curious because i hear “it’s always DNS” a lot and that’s not my experience at all – I’ve found that some networking issues are caused by DNS and some aren’t.
It does feel like weird/inexplicable issues are disproportionately likely to be caused by DNS though, because non-DNS problems are more straightforward to diagnose.
This was possibly a reference to https://www.cyberciti.biz/humour/a-haiku-about-dns/
Remember kids, don’t
dig,drill!nslookuporpingif you REALLY have toCould you elaborate on that?
https://nlnetlabs.nl/projects/ldns/about/ mentions DNSSEC support and
…but as we are not talking about testing DNS implementations, that does not seem too relevant? What other advantages does
drillhave compared todig?