I agree that it sounds like a resolver problem, but I don't think that is the
solution. Indeed, somebody having tried to install bind's resolver could
actually be the cause of the problem.
Now that Sun has come out with sets of Solaris patches to bring its version of
the nameserver and resolver up to bind 4.9.3 level, there is little reason to
want to replace the resolver. There are certainly good reasons to replace the
nameserver with the one from bind 4.9.4-P1 (*not* -REL) or 4.9.5-T6B. But the
resolver works well enough, and it is so closely tied in with the nameservice
switch and the dynamic loader that it is much safer just to leave it well
alone.
My recommendation would be to back out any replacement resolver installation,
so that you're sure you have a clean as-distributed version. Apply Sun's
patches. Perhaps rebuild tcl and tk. Then try again with scotty.
--
Dr George D M Ross, Department of Computer Science, University of Edinburgh
Kings Buildings, Mayfield Road, Edinburgh, Scotland, EH9 3JZ
Mail: gdmr@dcs.ed.ac.uk Voice: +44 131 650 5147 Fax: +44 131 667 7209
PGP: 1024/B74A4F7D 14 E8 B3 00 20 04 68 F8 95 40 CB 36 A4 D4 FA 90