DNS pre-validation step

Avatar
Scott Barclay

Hi Nerdio Team,

I’d like to suggest a much-needed improvement to the AVD host pool deployment workflow in Nerdio Manager for MSP.

Currently, if a linked network is configured with incorrect or non-functional DNS servers (e.g., DNS IPs that don’t point to valid domain controllers for the specified domain), the host provisioning process proceeds until the domain join step, where it fails with a generic error like `0x54b`. This causes unnecessary delays, confusion, and wasted deployment time.

It would be far more efficient if Nerdio performed a DNS pre-validation step at the time of host pool creation or host addition. This could include:

- A basic `nslookup` or `_ldap._tcp.dc._msdcs.<domain>` resolution test using the configured DNS servers.
- A warning if Azure default DNS (168.63.129.16) is detected on a domain-joined deployment.
- A validation check comparing the AADS DNS IPs from Azure Domain Services to what’s configured in the Linked Network.

Catching these misconfigurations early in the process would save significant troubleshooting effort and improve the user experience.

Thanks for your continued development and support of Nerdio Manager — this enhancement would be a big help.

Best regards,  
Scott Barclay  
Senior Engineer, Main Advantage
 

4

Comments (2 comments)

Sort by
0
Avatar
Jason Bridgeman

I think this was a glitch this morning and over the weekend.
We had a host pool try to reimage on Sunday morning.
It continues to restart the task from Sunday morning up to Monday morning and continued to fail at the domain join task.
Normally I would scroll down to the bottom of the domain join error, find the error code, look up the code to see what the issue is, and resolve it. In this case, I have never seen the error in Nerdio be filled with so much text.
It was essentially saying our "client.onmicrosoft.com" domain is not a valid domain. I checked the network and DNS. All were good. What I ended up doing was remove the saved credentials in the Nerdio settings and readded them. This got the pool to add the VM to the domain.

But you are correct. Some checks and balances would be good to have in place. It would also be nice to have some alerts if a pool continues to have issues trying to reimage.

0
Avatar
Carl Long
Thank you for your feature request—your input helps shape our roadmap.

Next steps:
     • We will review your request and update its status as it moves through the evaluation process.
     • If we need more details, we'll reach out in the comments.

We also welcome additional feedback and votes from the community.

Please sign in to leave a comment.