Closed bwbroersma closed 5 months ago
Make a fool proof configuration:
$ dig +time=2 +tries=1 @dev-docker.batch.internet.nl version.bind TXT chaos +short "unbound 1.19.1"
$ dig +time=2 +tries=1 @dev.batch.internet.nl version.bind TXT chaos +short ; <<>> DiG 9.16.48-Debian <<>> +time +tries @dev.batch.internet.nl version.bind TXT chaos +short ; (2 servers found) ;; global options: +cmd ;; connection timed out; no servers could be reached
$ dig +time=2 +tries=1 @batch.internet.nl version.bind TXT chaos +short ; <<>> DiG 9.16.48-Debian <<>> +time +tries @batch.internet.nl version.bind TXT chaos +short ; (2 servers found) ;; global options: +cmd ;; connection timed out; no servers could be reached
Proposal: make the startup command a shell that checks the ENABLE_BATCH flag, and if so then exit 0;. Hopefully this works with the health monitoring.
ENABLE_BATCH
exit 0;
This can be done in the entrypoint script docker/unbound/entrypoint.sh..
docker/unbound/entrypoint.sh
Removed the release blocker, since the config of 127.0.0.1 and ::1 would also 'work'.
127.0.0.1
::1
Make a fool proof configuration:
Proposal: make the startup command a shell that checks the
ENABLE_BATCH
flag, and if so thenexit 0;
. Hopefully this works with the health monitoring.This can be done in the entrypoint script
docker/unbound/entrypoint.sh
..