Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Install a command-line DNS tracing tool UNIX
There is a useful command-line utility known as 'dnstracer' written by Edwin Groothuis. dnstracer is available (in source code form, requiring compiling) from his web site.

It shows you which servers are responding to your DNS queries: those that have cached info and those which have the authoritative info. It seems like this would be very useful for debugging DNS problems.

I had no difficulty at all in compiling this. Following the instructions in the README, I ran ./configure and then make. I already had the Developer Tools from Apple, which are required to compile source code.
    •    
  • Currently 2.50 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (2 votes cast)
 
[7,544 views]  

Install a command-line DNS tracing tool | 10 comments | Create New Account
Click here to return to the 'Install a command-line DNS tracing tool' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Getting it to work...
Authored by: Supernova on Apr 02, '02 02:55:54AM
Ummm... I ran ./configure and make , but I didn't get it installed. Help?

( make install returned errors, but I don't know if I was actually supposed to run this - it listed it in the readme, but it was talking about straight linux).

Thanks

[ Reply to This | # ]
no man page
Authored by: macubergeek on Apr 02, '02 05:40:16AM

installed just fine but no man page installed though.
I have both Dev tools and Darwin tools installed though. Darwin tools gives you additional header files. Using both really helps compiling.



[ Reply to This | # ]
Getting it to work...
Authored by: sekalreed on Apr 02, '02 09:27:11AM

Try this:
./configure
make
sudo make install

You need the sudo because it has to install the binary in /usr/local/bin/ and the man page in /usr/local/man/man8/ which should be only accessible if you're an admin. It compiled and ran fine on 10.1.3 with the December Dev Tools.



[ Reply to This | # ]
Getting it to work...
Authored by: babbage on Apr 02, '02 10:11:39AM
The standard build-from-source procedure for most Free/Open software is, once you've downloaded & unzipped/unpacked the source:
./configure
make
make test
sudo make install

There are often parameters you can feed to the configure script -- try adding a "--help" to see what ones are available, then substitute the first line with the customized version like, say (making this up)

./configure --help
./configure --prefix=/usr/local --datadir=/var/dat/pkg --with-x
make
make test
sudo make install

Flags like the above would tell the system where to place the program, where it's datafiles should go, and should enable X-Windows support. Once configure finishes, it creates some customized scripts that drive the rest of the process, and that process is begun with the 'make' command. Once that finishes -- and it can take a while -- then run 'make test' to verify that no errors came up (not all packages include tests, but it's good to run this if you can). If the test step goes well, then apply the package to your system, using superuser privileges, with "sudo make install". Once that finishes, the software is added to your system, and can be used when you open a new terminal (or update your path with the "rehash" command).

[ Reply to This | # ]

Getting it to work...
Authored by: sevenov9 on Apr 04, '02 11:35:09AM

How come when ever I try the make command, it always says "make: *** No targets. Stop."..?



[ Reply to This | # ]
anybody having a compiled version
Authored by: zmagyar on Apr 02, '02 03:49:45AM

I don't have the dev tools pls mail me zmagyar@orchestra.de
Thanks



[ Reply to This | # ]
anybody having a compiled version
Authored by: oeyvind on Apr 02, '02 06:02:39AM

Get yours at ADC, http://developer.apple.com/



[ Reply to This | # ]
Here is one
Authored by: Bishop on Apr 02, '02 02:51:16PM

You can get a compiled version at www.e.kth.se/~e98_aar/dnstrace.sit



[ Reply to This | # ]
fink
Authored by: bhines on Apr 02, '02 10:47:13PM

I'll make a fink package... have about 10 so far.. If you guys can compile it, you can make fink packages, it's easy :)



[ Reply to This | # ]
Install a command-line DNS tracing tool
Authored by: SimonDorfman.com on Mar 27, '04 03:39:40AM
This hint didn't work for me. Maybe 10.3 broke something with dnstracer. So I installed dnstracer using fink and finkcommander. One caveat: dnstracer wont show up in fink commander until you follow these directions to make fink search the unstable tree:
Q5.8: There's this package in unstable that I want to install, but the fink command just says 'no package found'. How can I install it?

A: First make sure you understand what 'unstable' means. Packages in the unstable tree usually have not been tested by more than a few people. For that reason, Fink doesn't search the unstable tree by default. If you do enable unstable, please remember to e-mail the maintainer if something works (or even if it doesn't). Feedback from users like you is what we use to determine if something is ready for stable! To find out the maintainer of a package, run fink info .

Packages often have dependencies, and packages in unstable often depend on other packages in unstable. For that reason, it is best to activate all of unstable.

If you want Fink to use all of unstable, edit /sw/etc/fink.conf, add unstable/main and unstable/crypto to the Trees: line, and then run fink selfupdate; fink index.

If you only want one or two specific packages, and nothing else from unstable, then you need to switch over to CVS updating (i.e. use fink selfupdate-cvs), because rsync only updates the trees that are active in your fink.conf. Edit /sw/etc/fink.conf and add local/main to the Trees: line, if not present. Then you'll need to run fink selfupdate to download the package description files. Now copy the relevant .info files (and their associated .patch files, if there are any) from /sw/fink/dists/unstable/main/finkinfo (or /sw/fink/dists/unstable/crypto/finkinfo) to /sw/fink/dists/local/main/finkinfo. However, note that your package may depend on other packages (or particular versions) which are also only in unstable. You will have to move their .info and .patch files as well. After you move all of the files, make sure to run fink index, so that Fink's record of available packages is updated. Once you're done you can switch back to rsync (fink selfupdate-rsync) if you want.



[
Reply to This | # ]