See thread "Woody IPv6 problem finally, really, solved".
On Monday 23 September 2002 19:39, Frans Pop wrote:
> I'm having an annoying problem with exim every time "exim -q" is run by
> cron. Exim then causes two DNS query's to my local nameserver, namely for:
> - galadriel.fjphome.nl (the correct
See thread "Woody IPv6 problem finally, really, solved".
On Monday 23 September 2002 19:39, Frans Pop wrote:
> I'm having an annoying problem with exim every time "exim -q" is run by
> cron. Exim then causes two DNS query's to my local nameserver, namely for:
> - galadriel.fjphome.nl (the correct
On 24 Sep 2002, 23:42:10, Frans Pop wrote:
> I have checked everything again with your suggestions, but when I do
> "sudo -u mail exim -q" (to emulate crontab) I still get the following in
> querylog on my nameserver:
> XX+/10.19.66.21/galadriel.fjphome.nl//IN
> XX+/10.19.66.21/galadriel/
Frans Pop writes:
> I also get the second line when I do "dig galadriel -t ". Could it be
> Exim does not request "galadriel" but looks explicitly for "galadriel."?
> I get nothing in querylog when I do "ping galadriel". So it may also be
> that ping gets resolved locally (through files), but
Doug (and anybody else...),
Thnx for your reply to my questions and for your suggestions.
That's what I thought! I've been playing around with these settings for
several weeks now, reading docs and configfiles, but no go.
I have checked everything again with your suggestions, but when I do
"sud
5 matches
Mail list logo
