The short answer is “no … there is no recursive validation; no there is no CAB or Cabana magic to exploit (that I can think of).”

 Given this structure I would be tempted to extend the Customer object with Address and Country properties that reach across to the dependent objects … in essence, I’d flatten this out from the Customer object consumer’s perspective.  I’m not sure if this is the right path … it’s dangerous if there are other routes to the address or if you allow people to modify Country. But, assuming this is ok,  I’d add validations to those custom properties and you would bind to “aCustomer.Street” rather than “aCustomer.Address.Street”.

Of course you also have to manage this Aggregate … you have to make sure any change to the address is also a change to the parent customer (for concurrency purposes) and then save them together when you make a change in the address. 

I’m speaking really fast here and gliding over theory and details.

I would also reconsider if this kind of thing was happening EVERYWHERE. In that case, I’d want to look at a more generalized approach.

Anyway, this is a short peek into the matter and, if it shines adequate light on the path great; if not, we can refine.