Merge pull request #252055 from brianlehr/patch-64

Update custom-ip-address-prefix.md

Author: prmerger-automator[bot]

articles/virtual-network/ip-services/custom-ip-address-prefix.md

@@ -59,6 +59,8 @@ When ready, you can issue the command to have your range advertised from Azure a
 
 * The advertisements of IPs from a custom IP prefix over an Azure ExpressRoute Microsoft peering isn't currently supported.
 
+* Custom IP prefixes don't support Reverse DNS lookup using Azure-owned zones; customers must onboard their own Reverse Zones to Azure DNS
+
 * Once provisioned, custom IP prefix ranges can't be moved to another subscription. Custom IP address prefix ranges can't be moved within resource groups in a single subscription. It's possible to derive a public IP prefix from a custom IP prefix in another subscription with the proper permissions as described [here](manage-custom-ip-address-prefix.md#permissions).
 
 * IPs brought to Azure may have a delay of up to a week before they can be used for Windows Server Activation.