Glad it worked for you.

You added your reverse lookup zones for your internal IP subnets also (i.e. 168.192.in-addr.arpa)? Just wanted to make sure.

Do you happen to have Umbrella Protection enabled in your MX Threat Protection settings? We experienced a similar problem a couple of years ago and ultimately figured out that we needed to add our internal reverse lookup zones to the exclusion list ...