A VM in an Azure virtual network can resolve names in the private DNS zone contoso.com but cannot resolve names in the public Azure DNS zone adatum.com. You created a public Azure DNS zone named adatum.com and a private Azure DNS zone named contoso.com, and you linked contoso.com to the virtual network. VM1 can resolve internet hosts. What should you do to allow VM1 to resolve names in adatum.com?

The correct answer is to configure the name servers for adatum.com at the domain registrar. For a public Azure DNS zone like adatum.com to be resolvable from the internet (and by extension, by a VM that can resolve internet hosts), its name servers must be registered with the domain registrar where adatum.com was purchased. This directs DNS queries for adatum.com to Azure's DNS infrastructure. Updating the DNS suffix on VM1 to adatum.com would not help, as this setting is for internal network resolution and doesn't affect how public DNS queries are routed. Creating an SRV record in the contoso.com zone is irrelevant; SRV records are for service location, and placing it in contoso.com wouldn't enable resolution of adatum.com. Modifying IAM settings for the link to contoso.com is also irrelevant; IAM controls access to Azure resources, not DNS resolution paths for public zones.