Too many CNAMEs when looking up CAA

@Nayar Please see Legacy CAA Implementation

You have a loop per the CAA RFC:
nayarweb.com is CNAME’d to haproxy.nayarweb.com. Which when climbed will result in a lookup for nayarweb.com's CAA record, which results in a CNAME to haproxy.nayarweb.com and so on.