@schoen Thanks! I did not know it any of this info was sensitive so i just redacted everything.
@cpu Thanks for the help. If I correctly understand what you wrote the bug only made the error pop out different and had nothing to do with the CAA lookup failure itself. Do you have any pointers on that? The hostingprovider for that domain does not yet support CAA records, could that be the problem? or do I need to look elsewhere? Any help would be much appreciated.