They're free! There is no additional cost for reverse DNS records or queries.
Yes. Once you set the reverse DNS property for your Public IP Address, Azure manages all the DNS delegations and DNS zones required to ensure that reverse DNS record resolves for all internet users.
No. Reverse DNS is an opt-in feature. No default reverse DNS records are created if you choose not to configure them.
FQDNs are specified in forward order, and must be terminated by a dot (e.g., "app1.contoso.com.").
Where the validation for reverse DNS checks fail, the service management operation will fail. Please correct the reverse DNS value as required, and retry.
Reverse DNS is not supported for Azure Websites. Reverse DNS is supported for Azure Virtual Machines.
No. Azure supports a single reverse DNS record for each Public IP Address. Each Public IP Address however can have their own reverse DNS record.
No. At this time, reverse DNS records are supported for IPv4 Public IP Addresses only.
Can I configure a reverse DNS record for my Public IP Address without having a DomainNameLabel specified?
No. To leverage reverse DNS records for your Public IP Addresses, you must specify the DomainNameLabel property.
No. Azure Compute services do not support sending emails to external domains.