Micheal wrote:
My suspicion is related to the known issue with Win32 and Net-DNS 0.59.
I think you are seeing negative PTR lookups because Net-DNS is timing out.
Could you try to downgrade to 0.57?
Evan wrote:
Downgrade complete. Will have same high-network-activity conditions again
later this
Evan wrote:
I idly did a search in my logfile just now for ptr missing (running
in logging only mode for ptr check) and was interested to see, again,
several IPs where dnsstuff reports valid PTR.
Bummer.
This machine today has not been straining itself in any way. When
under heavy load
I think it is not worth to put so much effort in it. Just shut it
off. ASSP is built to grap the resources you free by that. If it goes
blind it will better hear ))).
fritz
-
Take Surveys. Earn Cash. Influence the Future
Micheal wrote:
My suspicion is related to the known issue with Win32 and Net-DNS 0.59.
I think you are seeing negative PTR lookups because Net-DNS is timing out.
Could you try to downgrade to 0.57?
Downgrade complete. Will have same high-network-activity conditions again later
this week, and
From: Evan Eggers [EMAIL PROTECTED]
Sample IP addresses from earlier today reported as PTRmissing by ASSP, but
having valid PTR according to dnsstuff are:
208.61.234.147
151.124.247.101
199.230.26.212
Perhaps DNSStuff is more persistent but when i tried using NSLookup from the
command prompt of
brougham Baker wrote:
From: Evan Eggers [EMAIL PROTECTED]
Sample IP addresses from earlier today reported as PTRmissing by ASSP, but
having valid PTR according to dnsstuff are:
208.61.234.147
151.124.247.101
199.230.26.212
Perhaps DNSStuff is more persistent but when i tried using
From: Micheal Espinola Jr [EMAIL PROTECTED]
208.61.234.147
151.124.247.101
199.230.26.212
Perhaps DNSStuff is more persistent but when i tried using NSLookup from
the
command prompt of a windows workstation they all timed out. I tried
known-good addresses and they worked properly.
brougham Baker wrote:
The known good ones answer instantly as I would expect (they are also not my
ISP's servers and are unlikely to be cached by me at a least). It's just the
above addresses that didn't answer for me. I tried using UDP, switching to
TCP resolution does get answers eventually-
- Original Message -
From: Micheal Espinola Jr [EMAIL PROTECTED]
To: Questions and Answers for users of ASSP Anti-Spam SMTP Proxy
assp-user@lists.sourceforge.net
Sent: 09 January 2007 16:58
Subject: Re: [Assp-user] Incorrect PTRmissing?
brougham Baker wrote:
The known good ones
Which OS and version of Net-DNS?
--
ME2 (mobile)
-Original Message-
From: Evan Eggers [EMAIL PROTECTED]
Date: Monday, Jan 8, 2007 6:44 pm
Subject: [Assp-user] Incorrect PTRmissing?
N00b here...
First of all, my hat is off to all of you who have made ASSP what it is
today... just
Hi Micheal,
Windows Server 2003, Net-DNS 0.59. I should also say that during the time the
problem manifested, I had a lot of network activity (mostly UDP) on this
machine even though the CPU was idling along at less than 20%. Makes me wonder
whether PTRmissing reports a fail when in fact the
Evan Eggers wrote:
Hi Micheal,
Windows Server 2003, Net-DNS 0.59. I should also say that during the
time the problem manifested, I had a lot of network activity (mostly
UDP) on this machine even though the CPU was idling along at less than
20%. Makes me wonder whether PTRmissing reports a
12 matches
Mail list logo
