
		     TO DO LIST FOR DOMTOOLS - VERSION 1.3

* digoutany.awk script foolishly assumes that SOA and WKS records always have
  parenthesized arguments spanning multiple lines.  Also assumes every other
  RR type does _not_ have parentheses and multi-lines.  Use the code from the
  awk script subzone.awk or subdom.awk to do this right.

* subdom2: if zone cse.nau.edu. has RRs for sub-sub-sub-domain type thing
  and we aren't going to call subdom2 recursively because its in this zone,
  then loop through all the "sub" domain parts and just print them.
  i.e., if you have a record like,
	pab.wow.gog.cse.nau.edu.  IN  A  1.2.3.4
  then "subdom -r cse.nau.edu." should output this:
	cse.nau.edu.
	gog.cse.nau.edu.
	wow.gog.cse.nau.edu.


CHECK THINGS FOR ALL DOMTOOLS:

     *	Any script that runs "ns" then uses "head -1" to get a name server,
	should replace that code with a for loop on all the nameservers,
	and "break" out of the loop if found one that works.  That way we
	try all the nameservers.  Also use a variable "noservers" to check
	just outside the loop if we ever found a good nameserver to query.
	If not, echo "error msg" >&2 and exit 1.

     *	Any time after we create a /tmp file ($TMP), if we error & exit,
	we must also "rm -f $TMP" !

     *	Some nameservers just lock up (well, >1min at least, never waited
	much longer) for certain queries.  Look at domain rn.com., its
	primary nameserver schizo.samsung.com. which is up and running does
	not return anything -- just locks up.  Maybe I need to implement a
	time-out somehow on every dig call?  1. does dig have timeout?
	2. could simply write a small C prog that sets alarm, fork&execv dig
	blindly passing in argv[], and if alarm handler called then kill the
	dig process and exit with error.  hmm, leave this for last!


BE CAREFULS

* Weirdity in bourne shell that if you pipe anything into a while statement
  and do variable assignments inside, the variables get reset outside the
  while loop!  This nailed me in the localad tool (ended up using a /tmp
  file to pass stuff back out - yuck).  "Kids don't try this at home":

		#!/bin/sh
		wow=1
		echo hello | wow=2
		echo $wow

  Acts just like a sub-shell, however the PID is the same as the outer shell.
  How annoying.
