Gluetun - is this log OK?

[aaany 0]

Hi!

I'm using Gluetun in Unraid docker.
Everything seems to work well (good speeds, port forwarding works), although it seems like Gluetun is reconnecting quite often.

I looked in the log and I see that I'm getting "start of service (unbound 1.17.1). - I'm not sure what that means.
And I'm getting quite a bit of unhealthy/healthy messages.
Is this log OK?

Thank you in advance!
 

023-07-03T22:23:12Z INFO [ip getter] Public IP address is 134.19.179.171 (Netherlands, North Holland, Amsterdam)
2023-07-03T22:23:12Z INFO [dns over tls] downloading hostnames and IP block lists
2023-07-03T22:23:13Z INFO [dns over tls] stopping
2023-07-03T22:23:13Z INFO [dns over tls] using plaintext DNS at address 10.128.0.1
2023-07-03T22:23:13Z INFO [dns over tls] starting
2023-07-03T22:23:13Z INFO [dns over tls] downloading DNS over TLS cryptographic files
2023-07-03T22:23:13Z INFO [dns over tls] downloading hostnames and IP block lists
2023-07-03T22:23:14Z INFO [dns over tls] ready
2023-07-03T22:23:18Z INFO [dns over tls] init module 0: validator
2023-07-03T22:23:18Z INFO [dns over tls] init module 1: iterator
2023-07-03T22:23:18Z INFO [dns over tls] start of service (unbound 1.17.1).
2023-07-04T02:09:27Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup github.com: i/o timeout
2023-07-04T02:09:29Z INFO [healthcheck] healthy!
2023-07-04T09:00:22Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup github.com: i/o timeout
2023-07-04T09:00:23Z INFO [healthcheck] healthy!
2023-07-04T09:37:31Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup github.com: i/o timeout
2023-07-04T09:37:32Z INFO [healthcheck] healthy!
2023-07-04T10:23:11Z INFO [ip getter] Public IP address is 134.19.179.171 (Netherlands, North Holland, Amsterdam)

[OpenSourcerer 1435]

Looks a bit like latency problems with the DoT provider you're using. Or is it AirDNS?
In any case, the timeouts are sporadic and usually correct themselves in the next lookup, it seems. It looks ugly in the log, but I don't see a problem.

[aaany 0]

4 hours ago, OpenSourcerer said:

Looks a bit like latency problems with the DoT provider you're using. Or is it AirDNS?
In any case, the timeouts are sporadic and usually correct themselves in the next lookup, it seems. It looks ugly in the log, but I don't see a problem.

Thank you for your input. I'm glad there is no problem.
Yes, It's AirDNS.