ECA-6138, each CAA lookup for a certificate SAN is made in parallel. This will probably cause the log entries written with log4j to appear "huller om buller" making the log output harder to read.
Instead of sending a log entry to log4j directly, we should queue them in for example a ConcurrentHashMap<String, LinkedList<String>> which maps a particular domain name to a list of log messages for that domain, and then print this map before exiting the CAA validator.
There is already a 'log' method in CaaDnsLookup we can use.
To make debugging of our customers' issues easier and avoid confusing them, this should probably be fixed before we release EJBCA 6.10.