Resolve Name Resolution Issue
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
Your company registers a domain name of contoso.com.
You create an Azure DNS zone named contoso.com, and then you add an A record to the zone for a host named www that has an IP address of 131.107.1.10.
You discover that Internet hosts are unable to resolve www.contoso.com to the 131.107.1.10 IP address.
You need to resolve the name resolution issue.
Solution: You add an NS record to the contoso.com zone.
Does this meet the goal?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B.A
Before you can delegate your DNS zone to Azure DNS, you need to know the name servers for your zone. The NS record set contains the names of the Azure
DNS name servers assigned to the zone.
https://docs.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dnsNo, adding an NS record to the contoso.com zone will not resolve the name resolution issue for www.contoso.com. An NS record is used to delegate a subdomain to a different DNS server, but it does not help resolve the IP address for a specific host.
To resolve the name resolution issue for www.contoso.com, you need to add a DNS record that maps the host name to the IP address. In this case, an A record has already been created for the host named www with the IP address of 131.107.1.10, which should be sufficient for resolving the name.
If Internet hosts are still unable to resolve www.contoso.com to the correct IP address, there might be an issue with the DNS configuration or propagation. It can take some time for DNS changes to propagate across the Internet, so it is possible that the changes have not fully taken effect yet. It is also possible that there are other DNS records that are conflicting with the A record for www.contoso.com, or that there is an issue with the DNS resolver configuration on the client side.
