There is much more to this than just reliability. I use dnsmadeeasy.com - they have been extremely reliable and full featured. The problem is with supporting naked domains (e.g. cnn.com as opposed to www.cnn.com). I know the standard approach is to add a CNAME from www to xxx.cloudapp.net and then use your dns provider's http redirection to redirect the naked domain to www.cloudapp.net. This is not really a viable solution though:

1) while dnsmadeeasy does provide this redirection. It (and almost all others) can only redirect http traffic. It cannot redirect https traffic. If someone tries to access https://cnn.com under this scheme - it will just fail as the DNS provider does not have https redirect because they do not have the certificate.

2) performance - multiple DNS lookups are required along with a redirection

3) SEO/SL IsoStorage - we had to make a choice some time ago which site would be our primary domain so as not to split our links. Another thing that forced this issue was Silverlight Isolated Storage (it sees www.cnn.com as a different domain than cnn.com and hence you get two different isostorage locations). We chose the naked domain to be our primary one and we use (the wonderful) urlrewrite to 301 redirect from www to naked domain as it CAN redirect https traffic as well.

In the end I had to just put in place an A record that pointed the naked domain to the IP of the xxx.cloudapp.net. (I know that this is not recommended.) MS needs to either provide an integrated DNS service that allows the naked domain to map to the xxx.cloudapp.net OR make it easier/safer to add an A record (just add a checkbox that says "don't change my IP without my approval/notice"). For now I have a pingdom.com account monitoring my site for uptime/downtime so if my ip changes i will get a notice within a minute and I can update DNS manually.

It's a common practice for WebApps to provide subdomain processing:

client1.domainApp.com,
client2.domainApp.com
...
clientN.domainApp.com

And using the Rewrite Module pass parameters to pages, so you can change LOGOS or CSS files to fit the desires of your clients.

So a Redirect is not an option as we want to keep the subdomain visible. Also to say that having a subdomain tells your client that he is not another parameter, but a special client.

I've read a lot of threads (http://social.msdn.microsoft.com/Forums/en-US/windowsazure/thread/1ba9ec61-10b5-464f-8f34-bb7d5fa84697/) and just cannot get a clear picture of how to do this. I think that implementing DNS or giving us information of DNS providers and AZURE accepting any subdomains (having a wildcard) will do it.

¿Correct?