Here is a normal day in the world of Hobbit DNS resolution...
DNS statistics:
# hostnames resolved : 17
# succesful : 17
# failed : 0
# calls to dnsresolve : 31
DNS lookups completed 1202826251.058136 0.072268
But now when there is a problem reaching the DNS server (I have two in
/etc/resolv.conf) it spikes up to...
DNS lookups completed 1202825989.913910 40.001908
Is there any way to set the DNS resolution timeout to something
smaller? Has anyone tried running bind9 on the Hobbit box itself and having
it hold cache locally? I have had two instances where Hobbit failed to
resolve DNS for a completely unknown reason, even while the DNS test on the
two hosts stay green!
What I hope to accomplish is finding the reasoning behind these DNS
failures. It will fail to resolve several unrelated domains (different NS
servers all together). My real confusion, though, it that Hobbit is asking
the same two boxes in /etc/resolv.conf for several domains - some of which
resolve, when some don't!
Thanks in advance!
Josh
--
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
Those who don't understand UNIX are condemned to reinvent it, poorly.
--- Henry Spencer