Found the problem.  /etc/resolv.conf on openvas appliance debian version seems
not supporting redundant dns configuration:

options timeout: 0.5
options attempts: 1
options rotate

Roberto


From: Openvas-discuss [mailto:[email protected]] On 
Behalf Of mlist
Sent: domenica 29 gennaio 2017 01.13
To: '[email protected]' <[email protected]>
Subject: [Openvas-discuss] Couldn't resolve target

Hi,
we have many "Couldn't resolve target ...", about one every 3 target check. 
This is very strange because
on the openvas virtual appliance pinging hostname reported as error works 
without problem

Roberto



_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to