|
Hi all , sorry for late reply, been out
of town.
I can confirm theat the qmail server is NOT a caching-nameserver
So I cleand the cache from the DNS servers , and all mail is now
working
Thanks again to all
Dave M
On 5/24/2013 7:11 PM, Cecil Yother, Jr. wrote:
On 05/24/2013 06:50 PM, Eric Shubert
wrote:
On
05/24/2013 11:26 AM, Aleksander Podsiadły wrote:
Dnia 2013-05-24, pią o godzinie 10:19
-0700, System Admin pisze:
Their Techs say we need to clear our
DNS Cache on our email server
IMHO there is no DNS cache on your email server. You should
clean your
DNS server cache:
8<--
rndc flush
8<-- EOT
I believe this is probably an effective answer, although there
are still some assumptions being make.
Addressing Eric B's first reply, I don't run nscd personally. I
figure that if/since there's a resolver running on the QMT host,
that would be caching entries, so nscd would be superfluous. I
could be wrong about this I suppose. If you're not running a
resolver on your QMT host, I suppose nscd might be helpful.
If you have the caching-nameserver package installed (a
localhost bind resolver) and properly configured ("nameserver
127.0.0.1" is first line in /etc/resolv.conf), then Alexsander's
reply should do the trick.
If you have the djbdns software running as your resolver, you
can probably find the appropriate command to clear its cache by
googling a bit.
Personally, I've begun using PowerDNS (pdns-recursor package) as
my QMT localhost resolver. I'd have to look up the command for
clearing its cache.
There are several options when configuring QMT's name
resolution. Up to now I don't believe there has been a 'stock'
configuration per se. If I were to choose one though, it'd be
the pdns-recursor package.
So bottom line here is, Dave needs to identify how his QMT's
name resolution is configured in order to get the appropriate
answer. A start would be by posting the contents of
/etc/resolv.conf, and if nameserver 127.0.0.1 is the first line,
then identify which (of 3 I've identified) resolver software
he's using.
HTH.
Thanks to everyone for their participation.
Have you tried to resolve the server in question using dig? Is
there a chance something else is going on? I would trust your
skill with your server before I was told by somebody unfamiliar
with your system that you must clear your cache. You may have a
totally unrelated problem.
--
|
