Your timeout is too short, at least for me... about digsec HOT 7 CLOSED

Never experienced timeout here but I think I should remove setting the timeout to 1, so it uses system default. If it is needed to be changed, it can be sent with +timeout= flag.

from digsec.

Or up it to 10 at least in case the user doesn't know what or where the system timeout is set. I've figured out how to use this through a proxy, and it adds real time delays. 10 for me is bare minimum.

Yes you can add +timeout but it's an annoyance if it timeout out-of-the-box.

from digsec.

Please do not close an issue if it is assigned

from digsec.

10 is an arbitrary number as 1. so keeping it to default and if needed setting it explicitly is the established method.

from digsec.

fixed with cbd2ec9

from digsec.

Sorry for closing it - I'll let you close them.

0.1 is an arbitrary number as 1.0 but < 10 pisses of your users if it doesn't work out-of-the-box.

from digsec.

I didnt say 0.1 . I havent experienced any issue with 1 second, and nobody ever complained about it with 1. Normally 1 second is a lot of time for a DNS request/response. The system default timeout is probably >= 60 seconds so it will work for anybody as long as their system is working with other applications.

from digsec.