I have a Windows virtual machine and Azure provides a DNS entry for it (e.g., myserver.cloudapp.net). This is great so I can always reach my VM. Unfortunately, apparently there is no corresponding PTR (reverse DNS) record created.
As such, you cannot operate a Microsoft Exchange Server on Windows Azure. Well, you can, but don't expect to be able to send email to anyone on AOL, Comcast, and a multitude of other domains. The reason is that these providers REQUIRE that the sending IP
address have a reverse lookup (PTR record) for the IP address from which email is being sent.
For simplicity (and a quick implementation), I suggest that there simply be a yes/no option for a PTR record (reverse DNS).
This is something absolutely needed. I'm considering Azure for migrating a server that needs to send email to users with notifications as part of the features of one App and without this I won't be able to do it.
this feature is a VERY BASIC item to sold Virtual machines, microsoft is out from marketplace, small stupid details, great diference thousand of client out, like microsoft invent IPAD in 2001, and sold 2000 units of xp tablets, Steve Jobs have more
timing..., 9 years latter sell the same, idea, and sell millions, wy? details... details... cosmetic details... usability details.. I am contractin at amazon, the next month I willbe hire anothers servers, if have reverse dns at that date, I willbe try
buy here, but... if I have very confortable at amazon clouds... i don know.... think about;