Argh! Typical...
The solution did have an internal DNS server to test a concept for a while,
and when it was removed, resolv.conf must have been emptied rather than
deleted. Will schedule another test and hopefully will be able to complete
this time...
I assume this behaviour is a Solaris resolver thing rather than an Exim one?
Many thanks for your assistance.
Tom
--
Tom Davidson
Virgin Support
Energis
----- Original Message -----
From: "Philip Hazel" <ph10@???>
To: "Tom Davidson" <exim-users@???>
Cc: <exim-users@???>
Sent: Tuesday, July 22, 2003 9:37 AM
Subject: Re: [Exim] strange failure to lookup IP address
> On Mon, 21 Jul 2003, Tom Davidson wrote:
>
> > The DNS lookup output is below as it was sent to stdout rather than
stderr.
>
> Yes, that's unfortunate, but that's what the resolver does when you turn
> on it's debugging switch.
>
> > I've checked for misconfigured DNS settings:
> > /etc/resolv.conf is empty (ie. file exists and is zero bytes)
> > hosts in /etc/nsswitch.conf is set to files
> >
> > It couldn't be as simple as an empty resolv.conf could it?! :-(
>
> Yes!
>
> --
> Philip Hazel University of Cambridge Computing Service,
> ph10@??? Cambridge, England. Phone: +44 1223 334714.
> Get the Exim 4 book: http://www.uit.co.uk/exim-book
>
>
