An administrator cannot create a new volume in Azure NetApp Files. The administrator receives an error that the DNS server is not available. What should the administrator do?

Question

Options

• AConfirm the network security groups allow connectivity
• BMake sure that the Volume and DNS server are in the same subnet
• CCreate a VNet service endpoint to the DNS server
• DConfigure subnet delegation for the VNet

• A
  84% (49)
• B
  2% (1)
• C
  5% (3)
• D
  9% (5)

Explanation

When an administrator receives an error that the DNS server is not available while trying to create a new volume in Azure NetApp Files, the first action should be to confirm that the network security groups allow connectivity. Here's the process: Check Network Security Group Rules: Verify that the network security group (NSG) associated with the subnet where Azure NetApp Files is located has rules that allow traffic to and from the DNS server, specifically permitting DNS query traffic (typically over port 53 for both TCP and UDP). Adjust NSG Settings if Necessary: If the current NSG rules are restrictive and do not allow DNS traffic, modify them to include the necessary allowances for DNS resolution. Test Connectivity: After updating the NSG settings, retry the volume creation to see if the DNS issue has been resolved.

No community discussion yet for this question.