Error "nslookup failed to resolve microsoft.com" while attempting to register Azure Storage Mover agent (machine is on-prem)

Question

Hello.

We are getting error "nslookup failed to resolve microsoft.com" while attempting to register Azure Storage Mover agent

The machine is on-prem Hyper VM. This is using option 3 "Test network connectivity". The Azure regition is "westus3". The agent VM machine is able to ping microsoft.com and other online resources, so DNS appears to be working. Using DHCP and the DNS server is 172.29.144.1.

Any suggestions?

Thank you,

Stephan

Answer 1

Hi @Stephan Avanozian

Welcome to Microsoft Q&A Forum and thanks for posting your query here!

As we see from the above error message that "nslookup failed to resolve microsoft.com" while attempting to register Azure Storage Mover agent it is due to which the DNS resolution is not working properly for Azure Storage Mover agent registration. Even though the machine is able to ping microsoft.com and other online resources, it is possible that the DNS resolution is not working properly for the Azure Storage Mover agent registration.

In order to resolve this issue, you can try the below suggestions.

1. Check the DNS configuration on the machine. Make sure that the DNS server settings are correct and that the machine is able to resolve DNS queries for other domains.
2. Try using a different DNS server. If the current DNS server is not working properly, try using a different DNS server to see if that resolves the issue.
3. Check if there is a firewall blocking DNS traffic. If there is a firewall, make sure that it is configured to allow DNS traffic to pass through.
4. Check if there is a network connectivity issue. If the machine is unable to connect to the internet, it may not be able to resolve DNS queries. Check the network connectivity and make sure that the machine is able to connect to the internet.
5. Try registering the Azure Storage Mover agent using the IP address of the Azure region instead of the DNS name. You can find the IP address of the Azure region by using the following command: nslookup -q=txt -class=CHAOS version.bind @ns1-1.azure-dns.com
6. Restart the DNS client service or the agent itself can help resolve transient issues.

If the issue still persists, even after following the above troubleshooting steps. Please reach out your networking administrator team or IT support.

I hope this helps in resolving the issue. Please let us know if there are any further questions, we will be glad to assist you closely.

Thanks!