Provide Reverse DNS (PTR records) for Virtual Machines
Currently, 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.
For simplicity (and a quick implementation by Microsoft), I suggest that you simply provide the option for a Reverse lookup or not. So if your VM is named myserver.cloudapp.net, then the reverse lookup on the current IP would return that name.
Is this something you can do quickly? I'm having to look at alternative solutions for my Exchange Server.
If user want to get hosted service DNS then using IP he/she can able to find DNS. As you can see in my case http://stackoverflow.com/questions/10612295/how-to-get-dns-name-from-rest-service-which-is-consumed-by-startuptask-of-azure/10622625#10622625
I would like to get details of DNS of webrole application but nslookup shows me that it doesn't exist. Using this somehow user can process on DNS and do some logic. In my case i would like to detect staging vs production using DNS without certificate & management API
When I develop e-mail related program, the server domain name should be found using reverse DNS lookup. So one of my program is not in Azure, but in my company Data Center.
This is a good suggestion, and definitely something we would like to offer. It’s part of our roadmap, although I can’t yet give a committed schedule.
Thank you for the feedback.
Mr. Softy try listening to your customers for once. We want to use you. We want to believe. But you keep letting us down at every step.
Let me run msft and see what happens. You guys need to change.
WE NEED THIS!!!!
When will it be available?
Bruno Bosshard commented
Is there still no movement on this? This is an essential requirement and beyond comprehension why that it is still not implement and not even announced!
aymen hajri commented
We need it asap guys!!
Is this for reeel? Just joined Azure and was planning to setup up a mailserver.... no PTR ability is BIG problem. What's the plan on getting this in?
It's been a year since Lester made the blatantly obvious suggestion. PTR records have become a requirement at this point for sending any emails and MSFT still doesn't think it's a high priority?
Any news on this? Having reverse DNS is critical for pretty much any public facing application, not only email.
Anton Karakulov commented
Our app have heavy email-load notifications to users, but without reverse DNS lookup we lost about 40% of emails (smtp and relays for most modern email services reject letters from domains without lookup record). =\
Can you predict how soon this issue will be realized?
Sigh, what useful application doesn't send a bit of email?
Erkko Välja commented
Been there and paid my school bills on it already. Also the fact is that because of it, You can't also host public DNS servers in Azure. This chapter from the roadmap should have been in the beginning of the journey! cmon MS!?!
Stephen McMaster commented
I agree totally. I currently run a Mail Server on Azure, however, I need to use SendGrid in order to ensure that outgoing mail is not identified as SPAM. It would be great if I didn't have to rely on these 3rd party providers.
this is not a "suggestion." this is a major bug within the azure ecosystem that renders any serious web-app crippled. microsoft needs to stop kidding itself about the seriousness of the issue. now after migrating to azure i must re-migrate to amazon. i did not need this ultimately unnecessary hassle, to put it very politely
we need ptr records ASAP!!!
Theofanis Giotis commented
Your comment simply declares tells to Microsoft's customers: "DO NOT EVER install Microsoft Exchange Server on an AZURE Virtual macnine because you CANNOT send email..."
Am I correct? If not, please correct me. If I am correct, please forward my comment to Steve Balmer.
A must have
It's not just Exchange. You can't run any email server on Azure. I currently have virtual servers at Rackspace and Atlantic. The only thing keeping me from moving them to Azure is the lack of reverse DNS.
If you add this to Azure please allow the user to define the reverse DNS value. Many email servers check to see if it matches the email server's domain.
For the last 30 years everyone knows that a STATIC IP needs a Reverse DNS (PTR record) to operate correctly.
I would like to be the CEO of Microsoft for one hour in order to talk to the Azure team...
migrated to AZure 1 month ago,
cannot use mail service due to PTR issue.
at least need simple 1 PTR record
"f your VM is named myserver.cloudapp.net, then the reverse lookup on the current IP would return that name"
we are thinking on migrating to another solution ((.
Naveed Nadir commented
Can we please have this now. It's been pending for more than a year.