Tsutomu Oyamada wrote:
> Our environment is a local mirror.
> However, it does not matter.
>
> I wanted to know if there is the case that the DNS TXT of ClamAV have
> not been updated for few days.
> Could it be possibe?
> Is this issue caused by the problem on our enviroment of querying DNS?
>
Our environment is a local mirror.
However, it does not matter.
I wanted to know if there is the case that the DNS TXT of ClamAV have
not been updated for few days.
Could it be possibe?
Is this issue caused by the problem on our enviroment of querying DNS?
The daily.cvd is updated in real time now
Was this freshclam log the result of checking your local mirror or a ClamAV
mirror? My guess would be that your local mirror was not up-to-date at the
time you ran freshclam from a client computer on your local network.
-Al-
On Fri, Nov 25, 2016 at 01:57 AM, Tsutomu Oyamada wrote:
>
> Sorry,
Tsutomu Oyamada wrote:
> ClamAV update process started at Sat Nov 5 05:01:15 2016
> Using IPv6 aware code
> Querying current.cvd.clamav.net
> TTL: 1797
> Software version from DNS: 0.99.2
> main.cvd version from DNS: 57
> main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60, builder:
Sorry,
The part of freshclam log is as follows;
ClamAV update process started at Sat Nov 5 05:01:15 2016
Using IPv6 aware code
Querying current.cvd.clamav.net
TTL: 1797
Software version from DNS: 0.99.2
main.cvd version from DNS: 57
main.cvd is up to date (version: 57, sigs: 4218790, f-level: 6
I realise English is not your main language and this is probably very difficult
for you to explain in what is to you a foreign language, but I don't think we
are able to figure out just what is not working ...
Tsutomu Oyamada wrote:
> In the present situation fail.
What is failing ?
Does you
In the present situation fail.
However, it did not fail one month ago.
I do not have log had been successful.
Want to know why should I fail to have succeeded in that.
On Thu, 24 Nov 2016 01:19:20 -0800
Al Varnell wrote:
> What is no longer working fine now?
>
> Do you have some example freshc
What is no longer working fine now?
Do you have some example freshclam.logs that show issues?
What ClamAV.net mirrors are you using?
$ host database.clamav.net
-Al-
On Thu, Nov 24, 2016 at 01:11 AM, Tsutomu Oyamada wrote:
>
> Hi, Al.
>
> Thank you for your reply.
>
> I tested in the followi
Read your freshclam.log file and see if there is any useful information in their
to help solve your problem.
dp
On 11/24/16 1:11 AM, Tsutomu Oyamada wrote:
Hi, Al.
Thank you for your reply.
I tested in the following environments.
ClamAV .net
| (Mirroring once every day)
My local up
Hi, Al.
Thank you for your reply.
I tested in the following environments.
ClamAV .net
| (Mirroring once every day)
My local update server
|(after 24 hours at mirroring)
freshclam
Worked fine until a month ago in this environment.
T.O.
On Wed, 23 Nov 2016 19:30:56 -0800
Al Varn
Thank for that very thorough explanation. I learned a lot.
But I suspect only somebody from ClamAV can answer the OP question about this,
although I don't really understand why it's being asked (i.e. if it was
changed, what impact could it have on the OP or was it simply asked out of
curiosity?
Al Varnell wrote:
> So I think I have the answer for this one. From my research it would seem
> that TTL values are set by the DNS server you are accessing, not by the
> ClamAV and is the same for all records on that server. You would have to
> check with the DNS ISP to find out if it has cha
I should add something you probably know but others may not - your nslookup
report states at the bottom that it is an non-authorative result which is why
you see the time remaining in your NS cache. If you include the IP of an
authorative NS server you will get the configured TTL.
Example: nsl
You are seeing the time remaining in the cached lookup on your system.
Subsequent queries will show the TTL falling with time.
dp
On 11/23/16 8:57 PM, Al Varnell wrote:
Thanks Dennis, for straightening me out on that.
Strangely I get a different answer using nslookup:
$ nslookup -type=txt -
Thanks Dennis, for straightening me out on that.
Strangely I get a different answer using nslookup:
> $ nslookup -type=txt -debug current.cvd.clamav.net
> Server: 10.0.1.1
> Address: 10.0.1.1#53
>
>
> QUESTIONS:
> current.cvd.clamav.net, type = TXT, cla
The TTL for the TXT record at current.cvd.clamav.net is 1800 seconds. You can
retrieve with curl or wget older versions of the signature by specifying the
full file name, for example daily-22590.cdiff
dp
On 11/23/16 8:03 PM, Al Varnell wrote:
On Nov 23, 2016, at 7:10 PM, Tsutomu Oyamada wrote
On Nov 23, 2016, at 7:10 PM, Tsutomu Oyamada wrote:
>
> We know CVD version information is published in DNS TXT record, this
> record's TTL values, 1800 seconds is currently is. This value is the
> same from the previous?
So I think I have the answer for this one. From my research it would seem t
I'm having difficulty following some of your questions and have no answers yet,
but what exactly is your mirror environment (IPs)?
Sent from Janet's iPad
-Al-
On Nov 23, 2016, at 7:10 PM, Tsutomu Oyamada wrote:
> Hi, All.
>
> We know CVD version information is published in DNS TXT record, this
Hi, All.
We know CVD version information is published in DNS TXT record, this
record's TTL values, 1800 seconds is currently is. This value is the
same from the previous?
Also in freshclam download old versions of CVD(one day ago) in local
mirror environment, we will succeed.
I thought I was bou
19 matches
Mail list logo
