Legacy reasons I guess. I this case it's a matter of a client not wanting to move off e-mail they use through their shared hosting provider, and me not wanting

Legacy reasons I guess. I this case it's a matter of a client not wanting to move off e-mail they use through their shared hosting provider, and me not wanting to touch that hornets nest. I'm fine with just setting up a CNAME record pointing somewhere, but I really do not want to change their DNS provider. As mentioned by someone else, last I tried, CF refused to "finalize" the setup and start building before I had setup the domain. I may have missed something though, I'll have to check again.