Skip to content

Latest commit

 

History

History
46 lines (32 loc) · 2.21 KB

create-ptr-for-smtp-service.md

File metadata and controls

46 lines (32 loc) · 2.21 KB
title description services documentationcenter author manager editor tags ms.service ms.devlang ms.topic ms.tgt_pltfrm ms.workload ms.date ms.author ms.custom
Configure reverse lookup zones for an SMTP banner check in Azure| Microsoft Docs
Describes how to configure reverse lookup zones for an SMTP banner check in Azure
virtual-network
virtual-network
genlin
WillChen
azure-resource-manager
virtual-network
na
article
virtual-network
infrastructure
10/31/2018
genli

Configure reverse lookup zones for an SMTP banner check

This article describes how to use a reverse zone in Azure DNS and create a Reverse DNS (PTR) record for SMTP Banner Check.

Symptom

If you host an SMTP server in Microsoft Azure, you may receive the following error message when send or receive a message from remote mail servers:

554: No PTR Record

Solution

For a virtual IP address in Azure, the reverse records are created in Microsoft owned domain zones, not custom domain zones.

To configure PTR records in Microsoft owned zones, use the -ReverseFqdn property on the PublicIpAddress resource. For more information, see Configure reverse DNS for services hosted in Azure.

When you configure the PTR records, make sure that the IP address and the reverse FQDN are owned by the subscription. If you try to set a reverse FQDN that does not belong to the subscription, you receive the following error message:

Set-AzureRmPublicIpAddress : ReverseFqdn mail.contoso.com that PublicIPAddress ip01 is trying to use does not belong to subscription <Subscription ID>. One of the following conditions need to be met to establish ownership: 
                    
1) ReverseFqdn matches fqdn of any public ip resource under the subscription; 
2) ReverseFqdn resolves to the fqdn (through CName records chain) of any public ip resource under the subscription; 
3) It resolves to the ip address (through CName and A records chain) of a static public ip resource under the subscription.

If you manually change your SMTP banner to match our default reverse FQDN, the remote mail server can still fail because it may expect the SMTP banner host to match the MX record for the domain.