Don't stop browsing after ~15min

[betamos]

I was surprised to discover that browse terminates, closing the entries channel, after ~15 minutes. Clearly, there was logic present handling the stop/timeout case in the original code. A simple repro can be achieved using the example:

time go run examples/resolv/client.go -wait 3600
2021/09/08 02:19:40 Failed to browse: periodicQuery: abort due to timeout
exit status 1
go run examples/resolv/client.go -wait 3600  0,39s user 0,17s system 0% cpu 14:45,19 total

I changed it the way I think is most intuitive, which is not timeout at all. My use case is a long-running application and while I could certainly browse multiple times, I don't see why. It looks like legacy from the original repo. Timeouts can be handled the usual way, using context.WithTimeout, if required.

[marten-seemann]

Thanks for catching this! This is a quite error-prone API this the backoff package is offering there, setting a default value of 15 minutes unless manually reset.

I think we might be able to get rid of this library altogether. Calculating an exponential backoff is really not that hard, even if you want to add some jitter. Will do so in a follow-up PR.