DNS tools for developers(viewdns.info)
viewdns.info
DNS tools for developers
http://www.viewdns.info/
16 comments
This is very useful, and to call it disappointing is rude to the creator of the tool. Why would you say something so negative just because it's not perfect? This is the problem with Hacker News these days - people can't wait to say something nasty.
I have edited my post to hopefully make it less "rude", that was certainly not my intention. I do want to point out, and I think I am not alone in this, that in 2012, lack of IPv6 support (at least at the basic level of parsing IPv6 addresses and showing AAAA records / reverse lookups) in a network tools suite doesn't make it "not perfect", it makes it "not useful".
Au contraire, if anything, consistent rudeness risks getting you hellbanned.
I don't think it's unreasonable or rude to state that one is disappointed that a tool doesn't have a feature. Especially an important feature such as IPv6! Given that the disappointment is that ViewDNS.info bills itself as "your one source for DNS tools", it doesn't entirely live up to it's own billing.
I don't think it's unreasonable or rude to state that one is disappointed that a tool doesn't have a feature. Especially an important feature such as IPv6! Given that the disappointment is that ViewDNS.info bills itself as "your one source for DNS tools", it doesn't entirely live up to it's own billing.
Why is having a valid criticism or critique considered rude?
If I was the creator I would welcome such feedback.
If anything I would say that's one of the positive aspects of Hacker News.
If I was the creator I would welcome such feedback.
If anything I would say that's one of the positive aspects of Hacker News.
It's a nice website, but developers would be more inspired to try tools such as dnrd which allows one to run multiple dns servers on one machine and reverse-proxy the requests.
Ex on my dsl modem where I love to test stuff:
dnrd-port53 -a 192.168.178.1 -m off -s 127.0.0.1:mydomain.com -s 127.0.0.2:local -s 127.0.0.4:fritz.box -s 127.0.0.4:178.168.192.in-addr.arpa -s 213.16.20.51 -s 213.188.172.70 -s 74.82.42.42 -u dns -R /tmp/dnrd -l
This runs dnrd (hardcoded to bind on port 53 - I sometimes use other ports), and case switch the requests : if it ends by .mydomain.com, it goes to 127.0.0.1 if it ends by .local, it goes to 127.0.0.2 if it ends by .fritz.box, it goes to 127.0.0.4 if it ends by .178.168.192.in-addr.arpa (reverse), it goes to 127.0.0.4 everything else goes to 213.16.20.51, 213.188.172.70, 74.82.42.42 : if one stops responding it's removed from the list and the others are used.
THAT is a tool for developpers.
Shameless plug : bind6.c on http://code.google.com/p/guylhem/source/browse/bind6.c : if you also have a fritzbox dsl modem, you can "force bind" its default dns server to a given ip:53 instead of *:53, allowing another servers on say 127.0.0.1 :
killall multid; LD_PRELOAD=bind6.so BIND_IPV6=::ffff:127.0.0.4 /sbin/multid -v -d -U -P
Ex on my dsl modem where I love to test stuff:
dnrd-port53 -a 192.168.178.1 -m off -s 127.0.0.1:mydomain.com -s 127.0.0.2:local -s 127.0.0.4:fritz.box -s 127.0.0.4:178.168.192.in-addr.arpa -s 213.16.20.51 -s 213.188.172.70 -s 74.82.42.42 -u dns -R /tmp/dnrd -l
This runs dnrd (hardcoded to bind on port 53 - I sometimes use other ports), and case switch the requests : if it ends by .mydomain.com, it goes to 127.0.0.1 if it ends by .local, it goes to 127.0.0.2 if it ends by .fritz.box, it goes to 127.0.0.4 if it ends by .178.168.192.in-addr.arpa (reverse), it goes to 127.0.0.4 everything else goes to 213.16.20.51, 213.188.172.70, 74.82.42.42 : if one stops responding it's removed from the list and the others are used.
THAT is a tool for developpers.
Shameless plug : bind6.c on http://code.google.com/p/guylhem/source/browse/bind6.c : if you also have a fritzbox dsl modem, you can "force bind" its default dns server to a given ip:53 instead of *:53, allowing another servers on say 127.0.0.1 :
killall multid; LD_PRELOAD=bind6.so BIND_IPV6=::ffff:127.0.0.4 /sbin/multid -v -d -U -P
robtex.com is my go-to for DNS/AS/IP info.
google.com domain report: http://www.robtex.com/dns/google.com.html#summary
google AS peering info: http://www.robtex.com/as/as15169.html#peer
netblock info: http://www.robtex.com/route/74.125.0.0-16---google.html
google.com domain report: http://www.robtex.com/dns/google.com.html#summary
google AS peering info: http://www.robtex.com/as/as15169.html#peer
netblock info: http://www.robtex.com/route/74.125.0.0-16---google.html
Very useful!
It seems this was posted by the developer of this site himself, so I've got a feature request: combining these tools. For example, you enter a domain name or IP address and you get the following information:
- DNS report
- Reverse IP
- Port scan
- Chinese/Iran Firewall test
- DNSSEC
- IP location (maybe of nameserver IPs as well?)
- PageRank check
- Traceroute
- Ping
- DNS records
- HTTP headers
- Spam DB lookup
- ASN
Adding this would make things a whole lot easier, I hope you will consider it!
It seems this was posted by the developer of this site himself, so I've got a feature request: combining these tools. For example, you enter a domain name or IP address and you get the following information:
- DNS report
- Reverse IP
- Port scan
- Chinese/Iran Firewall test
- DNSSEC
- IP location (maybe of nameserver IPs as well?)
- PageRank check
- Traceroute
- Ping
- DNS records
- HTTP headers
- Spam DB lookup
- ASN
Adding this would make things a whole lot easier, I hope you will consider it!
There's an API[1], so this is something one could throw together pretty easily, assuming there are no limits to prevent it.
[1] http://viewdns.info/api/
[1] http://viewdns.info/api/
I agree, or at least include the main info in one simple "IP info" page.
If this is interesting for you, you may also be interested in my http://www.oriontransfer.co.nz/gems/rubydns tools.
Seems a little buggy:
"Oops! Your SOA serial number (2012041402) doesn't seem to be in the recommended format (YYYYMMDDnn - where nn is the revision number)."
Looks like it's in that format to me?
"Oops! Your SOA serial number (2012041402) doesn't seem to be in the recommended format (YYYYMMDDnn - where nn is the revision number)."
Looks like it's in that format to me?
The command-line tools bundled with djbdns are nice (http://cr.yp.to/djbdns/tools.html & http://cr.yp.to/djbdns/debugging.html) and IMO are easier to use than dig.
http://www.dnsvalidation.com/ is also a nicely done site for checking DNS configuration.
http://www.dnsvalidation.com/ is also a nicely done site for checking DNS configuration.
The drill tool that NSD built atop ldns[1] is pretty sweet too. Some of the other ldns tools are quite useful too.
[1]: http://www.nlnetlabs.nl/projects/ldns/
[1]: http://www.nlnetlabs.nl/projects/ldns/
The DNS propagation checker -- is there an existing framework that this site interfaces or is it something that they rolled out on their own? I've seen some services that use a dozen of servers to run the check, but this is hardly sufficient ad it excludes the last mile (where all the fun stuff is).
I think it is especially amusing that (according to viewdns.info), dnssec.net itself does not have DNSSEC enabled (while it is producing a response for verisign.com for example). Thoughts on the virtues of DNSSEC? Why are you (not) using it?
I'm interested in more details about how the "Iran Firewall Test" works. It shows my site as blocked, while I can confirm it elsewhere, it would be nice to know how this determined that.
I suspect it's getting hammered at the moment -- the Iran check returned an error for me, and the Google page rank check for "google.com" or "yahoo.com" still reports "Sorry, we couldn't seem to find that domain in Google's cache."
To the developer: this is a great time to refine the error handling (plus scaling, of course). :)
E.g., make sure when the requests fail (for whatever reason) that it can report this back to the user clearly.
To the developer: this is a great time to refine the error handling (plus scaling, of course). :)
E.g., make sure when the requests fail (for whatever reason) that it can report this back to the user clearly.
Awesome! It's like dnsstuff but free again! Thanks!
I woulnd't say this is just for developers, I'm a sysadmin and this is definitely something I'll add to my toolbox.
http://mrdns.com/ is also good
I love the Chinese Firewall Test XD
+1 for having an API. I'm increasingly on a rampage to replace anything I currently have to do via GUI or web browser with something I can do via CLI or API. So much faster, more automatable, less visual fluff and cognitive overhead.
Cool! "Chinese Firewall Test"..
EDIT: for friendliness.