On 9/13/11 7:53 PM, Noel Jones wrote:
On 9/13/2011 9:03 PM, Bryan Burke wrote:
My logs show successful update sources in the last line, but not when there
is no update.
Ok, well I did check the output of the grep before posting the number of lines
on this
list, and all log entries mentioning that IP were failures. So there's still
*technically*
some gray area, in that, if it happened to query that IP successfully, and
there was no
update, we'd never know, but I'm guessing that would reveal a similar outcome.
There is no grey area. All connections are logged, both successful
and unsuccessful. When DNS reports there is no update available,
no connection is attempted and consequently there is no IP to log.
From a well-connected host near Nashville TN USA:
# tcping 88.198.67.125 80
88.198.67.125 port 80 closed.
I get identical "port 80 closed" results from several hosts on
various major USA ISPs.
I've just sent the URL to validator.wc3.org and got the same problem with this
message:
I got the following unexpected response when trying to retrieve
<http://88.198.67.125>:
500 Can't connect to 88.198.67.125:80 (connect: Connection refused)
I'm satisfied that site should be pulled from the list.
If you have your own DNS server you can create your own round-robin authorative
DNS server pointing to known to be reliable signature servers and which are
located where ever they may be. It takes very little time to set one up.
dp
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
